# RailCore Developers (remote · mcp.railcore.tech)

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

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.railcore.tech`: 74/100 (this document), [markdown](https://verifymcp.io/servers/tech-railcore-developers/developers-mcp.md), [page](https://verifymcp.io/servers/tech-railcore-developers/developers-mcp)

## Channel facts

- Endpoint: `https://mcp.railcore.tech/developers/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2264 tokens (~42/item across 53 items; 8 tools + 45 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http tech-railcore-developers 'https://mcp.railcore.tech/developers/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-railcore-developers": {
      "url": "https://mcp.railcore.tech/developers/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-railcore-developers": {
      "type": "http",
      "url": "https://mcp.railcore.tech/developers/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-railcore-developers]
url = "https://mcp.railcore.tech/developers/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-railcore-developers": {
      "type": "remote",
      "url": "https://mcp.railcore.tech/developers/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-railcore-developers --url 'https://mcp.railcore.tech/developers/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-railcore-developers:
    url: "https://mcp.railcore.tech/developers/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-railcore-developers": {
      "Transport": "http",
      "Url": "https://mcp.railcore.tech/developers/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-railcore-developers -t streamable-http -u 'https://mcp.railcore.tech/developers/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-railcore-developers": {
      "type": "http",
      "url": "https://mcp.railcore.tech/developers/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-20 (score 73)

First indexed and scored.

## MCP tools (8)

### `search_docs` (~116 tokens)

Search the RailCore API docs

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.

Input parameters:

- `kind` (string): Limit results to guides, endpoints or errors. Default: any.
- `limit` (integer): How many results, 1 to 10. Default: 5.
- `query` (string, required): What to look for, in plain words or an error code.

Output parameters:

- `catalog_generated_at` (string)
- `query` (string)
- `results` (array)

### `get_endpoint` (~136 tokens)

Get one RailCore API endpoint

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.

Input parameters:

- `detail` (string): summary (default) or full, which adds response fields and a response example.
- `endpoint` (string, required): An endpoint id (seat-availability), a method and path (GET /availability/seats) or a URL.

Output parameters:

- `availability` (string)
- `body_example_json` (string)
- `body_fields` (array)
- `catalog_generated_at` (string)
- `cost` (object)
- `description` (string)
- `docs_url` (string)
- `errors` (array)
- `id` (string)
- `markdown_url` (string)
- `method` (string)
- `notes` (array)
- `parameters` (array)
- `response_example_json` (string)
- `response_fields` (array)
- `scope` (string)
- `signing` (string)
- `signing_required` (boolean)
- `summary` (string)
- `title` (string)
- `url` (string)

### `get_code_sample` (~156 tokens)

Get a working code sample

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.

Input parameters:

- `endpoint` (string, required): An endpoint id, a method and path, or a URL.
- `language` (string, required): curl, node, python, php, go or java.
- `signed` (boolean): true for Growth, Scale and Enterprise keys, which must sign every request. Default: true only for endpoints that signing plans alone can use.

Output parameters:

- `catalog_generated_at` (string)
- `code` (string)
- `docs_url` (string)
- `endpoint_id` (string)
- `env_vars` (array)
- `language` (string)
- `notes` (array)
- `signed` (boolean)

### `explain_error` (~129 tokens)

Explain a RailCore API error

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.

Input parameters:

- `code` (string): The error code, such as QUOTA_NOT_SUPPORTED.
- `endpoint` (string): The endpoint the request went to, if known.
- `error_json` (string): The error response body. Remove any API key or secret first.
- `status` (integer): The HTTP status, such as 422.

Output parameters:

- `catalog_generated_at` (string)
- `category` (string)
- `code` (string)
- `docs_url` (string)
- `endpoints` (array)
- `fix` (string)
- `key_warning` (string)
- `known` (boolean)
- `meaning` (string)
- `retryable` (boolean)
- `status` (number)

### `get_plans` (~78 tokens)

Compare RailCore API plans

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.

Input parameters:

- `plan` (string): A plan name or id, such as Growth. Leave out to compare all plans.

Output parameters:

- `catalog_generated_at` (string)
- `plans` (array)
- `pricing_url` (string)
- `signing_rule` (string)

### `get_my_usage` (~58 tokens)

Your RailCore API usage

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.

Output parameters:

- `by_key` (object)
- `has_plan` (boolean)
- `key_count` (number)
- `limits` (object)
- `partial` (boolean): true: some counters could not be read, so figures may be low.
- `plan` (object)
- `pricing_url` (string)
- `this_month` (object)
- `unit` (string)

### `list_my_keys` (~68 tokens)

Your RailCore API keys

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.

Output parameters:

- `count` (number)
- `keys` (array)

### `try_endpoint` (~289 tokens)

Try a RailCore API endpoint

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.

Input parameters:

- `body` (string): 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"}]}.
- `endpoint` (string, required): A read endpoint: an id (search-stations), a method and path (GET /stations/search) or a URL.
- `max_requests` (integer): The most requests this try may count, 1 to 25. Default 1. Raise it only after the user agrees to the cost.
- `params` (object): 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.

Output parameters:

- `body_json` (string): The response body as text, cut near 32 KB.
- `docs_url` (string)
- `endpoint_id` (string)
- `error_code` (string)
- `error_message` (string)
- `method` (string)
- `ok` (boolean)
- `quoted_requests` (number): What this request was expected to count, before it was sent.
- `request_id` (string)
- `requests_counted` (number): From X-RailCore-Credits-Cost.
- `requests_remaining` (number): From X-RailCore-Credits-Remaining.
- `status` (number)
- `truncated` (boolean)
- `url` (string): The public URL of the same request.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-railcore-developers/developers-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73

## 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.

## Links

- Remote endpoint: https://mcp.railcore.tech/developers/mcp
- Website: https://railcore.tech/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/tech-railcore-developers/developers-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-railcore-developers/developers-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-railcore-developers/developers-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tech-railcore-developers/developers-mcp
