Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RailCore Developers

REMOTE · MCP.RAILCORE.TECH

Indian Railways API docs and code samples, plus your RailCore usage, keys and live test requests.

74 Trust /100

Last scanned (21 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2264 tokens (~42/item across 53 items; 8 tools + 45 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 73

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.railcore.tech/developers/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.railcore.tech CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 b3f68c5dfe5044b613fe3dfaaf4569c0
SANs: mcp.railcore.tech
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.railcore.tech. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tech. DS published 2185 13 Verified
railcore.tech. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.railcore.tech/developers/mcp Verified 200
http (plaintext) http://mcp.railcore.tech/developers/mcp HTTPS enforced 301 https://mcp.railcore.tech/developers/mcp
MCP tools · 8 exposed · ~1,030 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_error ~129

What a RailCore API error means and how to fix it. Pass the error code (QUOTA_NOT_SUPPORTED), the HTTP status, or the whole error response. Never paste an API key or signing secret; any key-shaped text is removed before it is read.

NameTypeReqDescription
codestring–The error code, such as QUOTA_NOT_SUPPORTED.
endpointstring–The endpoint the request went to, if known.
error_jsonstring–The error response body. Remove any API key or secret first.
statusinteger–The HTTP status, such as 422.
NameTypeReqDescription
catalog_generated_atstringyes–
categorystring––
codestring––
docs_urlstringyes–
endpointsarrayyes–
fixstringyes–
key_warningstring––
knownbooleanyes–
meaningstringyes–
retryableboolean––
statusnumber––

No examples provided.

get_code_sample ~156

Working code for a RailCore API endpoint in curl, Node.js, Python, PHP, Go or Java. Set signed to true for Growth, Scale and Enterprise keys, which must sign every request with HMAC-SHA256. Samples read the key from RAILCORE_KEY and the signing secret from RAILCORE_HMAC_SECRET, and work out their dates when they run.

NameTypeReqDescription
endpointstringyesAn endpoint id, a method and path, or a URL.
languagestringyescurl, node, python, php, go or java.
signedboolean–true for Growth, Scale and Enterprise keys, which must sign every request. Default: true only for endpoints that signing plans alone can use.
NameTypeReqDescription
catalog_generated_atstringyes–
codestringyes–
docs_urlstringyes–
endpoint_idstringyes–
env_varsarrayyes–
languagestringyes–
notesarrayyes–
signedbooleanyes–

No examples provided.

get_endpoint ~136

Details of one RailCore API endpoint: method and URL, parameters, what it costs in requests, the key scope it needs, which plans can use it and whether requests must be signed, response fields and the errors it can answer. Accepts an endpoint id (seat-availability), a method and path (GET /trains/{train_number}/live) or a full URL.

NameTypeReqDescription
detailstring–summary (default) or full, which adds response fields and a response example.
endpointstringyesAn endpoint id (seat-availability), a method and path (GET /availability/seats) or a URL.
NameTypeReqDescription
availabilitystringyes–
body_example_jsonstring––
body_fieldsarray––
catalog_generated_atstringyes–
costobjectyes–
descriptionstringyes–
docs_urlstringyes–
errorsarrayyes–
idstringyes–
markdown_urlstringyes–
methodstringyes–
notesarrayyes–
parametersarrayyes–
response_example_jsonstring––
response_fieldsarray––
scopestringyes–
signingstringyes–
signing_requiredbooleanyes–
summarystringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_my_usage ~58

Your RailCore API plan and this month's usage: requests used and left, the per-minute and per-day limits, use per API key and in the docs playground, and when the allowance refills. Requires sign-in to your RailCore account.

Input schema present but exposes no named parameters.

NameTypeReqDescription
by_keyobjectyes–
has_planbooleanyes–
key_countnumberyes–
limitsobject––
partialbooleanyestrue: some counters could not be read, so figures may be low.
planobject––
pricing_urlstringyes–
this_monthobject––
unitstringyes–

No examples provided.

get_plans ~78

RailCore API plans: monthly price in INR, requests a month, per minute and per day, which plans must sign requests, IP allowlists, and which include charts and jobs. Pass a plan name to see one plan.

NameTypeReqDescription
planstring–A plan name or id, such as Growth. Leave out to compare all plans.
NameTypeReqDescription
catalog_generated_atstringyes–
plansarrayyes–
pricing_urlstringyes–
signing_rulestringyes–

No examples provided.

list_my_keys ~68

Your active RailCore API keys: label, the first characters of the key, scopes, whether a signing secret is set, how many IP addresses are allowed, and when each was created, last used and expires. Never a full key or secret. Requires sign-in to your RailCore account.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes–
keysarrayyes–

No examples provided.

search_docs ~116

Search the RailCore Indian Railways API documentation: guides (authentication, request signing, rate limits, billing in requests), endpoint pages and error codes. Returns the best matching sections with links. Use it for any how-to question about the API.

NameTypeReqDescription
kindstring–Limit results to guides, endpoints or errors. Default: any.
limitinteger–How many results, 1 to 10. Default: 5.
querystringyesWhat to look for, in plain words or an error code.
NameTypeReqDescription
catalog_generated_atstringyes–
querystringyes–
resultsarrayyes–

No examples provided.

try_endpoint ~289

Send one real request to a RailCore API read endpoint with your account and return its answer: status, request ID, requests counted and left, and the response body. It counts against your plan like any API request, so ask the user first. max_requests caps what it may count (default 1); a request that would count more is refused before it is sent. At most 30 tries an hour. Requires sign-in to your RailCore account. The first try also asks permission to make test requests.

NameTypeReqDescription
bodystring–The JSON body as text, for the two POST endpoints only (batch-seat-availability, compare-journeys), such as {"journeys": [{"from": "BSL", "to": "ADI", "date": "2026-12-01"}]}.
endpointstringyesA read endpoint: an id (search-stations), a method and path (GET /stations/search) or a URL.
max_requestsinteger–The most requests this try may count, 1 to 25. Default 1. Raise it only after the user agrees to the cost.
paramsobject–Path and query parameters by name, every value as a string, such as {"q": "pune", "limit": "5"} or {"train_number": "12951"}. Dates as YYYY-MM-DD.
NameTypeReqDescription
body_jsonstringyesThe response body as text, cut near 32 KB.
docs_urlstringyes–
endpoint_idstringyes–
error_codestring––
error_messagestring––
methodstringyes–
okbooleanyes–
quoted_requestsnumberyesWhat this request was expected to count, before it was sent.
request_idstring––
requests_countednumber–From X-RailCore-Credits-Cost.
requests_remainingnumber–From X-RailCore-Credits-Remaining.
statusnumberyes–
truncatedbooleanyes–
urlstringyesThe public URL of the same request.

No examples provided.

Install

How do I install the RailCore Developers MCP server?

RailCore Developers is a hosted endpoint at https://mcp.railcore.tech/developers/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.railcore.tech

# add to Claude Code
claude mcp add --transport http tech-railcore-developers 'https://mcp.railcore.tech/developers/mcp'
Common questions

What is the RailCore Developers MCP server?

RailCore Developers is an MCP server listed in the public MCP registry as tech.railcore/developers. Indian Railways API docs and code samples, plus your RailCore usage, keys and live test requests. This page covers its hosted endpoint (https://mcp.railcore.tech/developers/mcp).

Is the RailCore Developers MCP server safe to use?

RailCore Developers scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the RailCore Developers MCP server expose?

RailCore Developers exposes 8 tools: search_docs, get_endpoint, get_code_sample, explain_error, get_plans, and 3 more. Their descriptions and schemas cost roughly 1,030 tokens of context every time the server is loaded.

Does the RailCore Developers MCP server require authentication?

No. We connected to RailCore Developers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RailCore Developers MCP server still maintained?

RailCore Developers is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the RailCore Developers MCP server?

VerifyMCP ran 13 checks on RailCore Developers, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.