Loading the registry…
Indian Railways MCP Server.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- indian-railways-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
17 findings · 9.2s
v0.3.74
8 findings · 1.5s
v0.1.0
10 findings · 4.0s
v0.1.0
0 findings · 4.0s
v0.71.0
138 findings · 0.3s
v2.3.8
140 findings · 1.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.5s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 19, 2026 | Flagged25 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 313 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 6 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
11 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/app.py, /repo/src/server.py · reported by cisco-skill-scanner
10 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/src/server.py · reported by nerlo-behavioral
4 GHSA-pw6j-qg29-8w7f
Files: /repo/requirements.txt, /repo/uv.lock, requirements.txt and 1 more · reported by osv-scanner, trivy
3 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock, requirements.txt · reported by agent-audit-kit
2 CVE-2024-47081
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-48379
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-48889
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-50181
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-50182
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-53365
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-53366
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-54121
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-62727
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66416
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66418
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66471
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-67221
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-67724
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-67725
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-67726
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-68146
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-10783
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-21441
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-22701
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-24486
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-25645
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-25990
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-27167
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28414
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28415
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28416
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28684
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-31958
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-35536
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-40192
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-40347
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42308
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42309
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42310
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42311
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42561
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-44431
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-4539
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-45409
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48545
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48710
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48817
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48818
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-49853
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-49854
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-49855
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-52869
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53538
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53539
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53540
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54058
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54059
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54060
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54282
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54283
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-55379
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-55380
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-55798
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59197
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59198
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59199
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59200
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59204
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59205
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59950
Files: requirements.txt, uv.lock · reported by trivy
2 GHSA-78cv-mqj4-43f7
Files: requirements.txt, uv.lock · reported by trivy
2 PYSEC-2025-119
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2025-265
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2025-266
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2025-267
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2025-61
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-107
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1374
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1375
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-140
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-141
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-161
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1616
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1617
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1618
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-165
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1852
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1872
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1941
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1942
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1994
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1996
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1997
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1998
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1999
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-211
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2132
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-215
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2178
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2179
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2249
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2250
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2251
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2252
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2253
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2254
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2255
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2256
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2257
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2270
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2275
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2280
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2281
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2287
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-248
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-249
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2874
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2987
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3036
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3037
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3038
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3039
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3040
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3041
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3387
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3388
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3389
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3451
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3453
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3454
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3482
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3483
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3493
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3494
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3495
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3496
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-63
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-64
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-65
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-66
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
1 AAK-DNS-REBIND-002
Files: requirements.txt · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: app.py · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: requirements.txt · reported by agent-audit-kit
1 AAK-SSRF-002
Files: src/server.py · reported by agent-audit-kit
1 FILE_MAGIC_MISMATCH
Files: /repo/requirements.txt · reported by cisco-skill-scanner
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: /repo/repo/README.md, SECURITY.md, /repo/SKILL.md · reported by cisco-skill-scanner, agent-audit-kit
2 The model did not answer for these findings.
Rules: CVE-2026-53537 · Files: requirements.txt, uv.lock · reported by trivy
High-severity risks include credential exposure and network egress.
The artifact contains high-severity findings, including potential credential access leading to network egress and Server-Side Request Forgery in `src/server.py`. A DNS rebinding vulnerability is present in `requirements.txt`. Additionally, numerous high-severity vulnerabilities are identified in the artifact's dependencies.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Showing 25 of 177; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.