# Railway MCP Server > Railway's official MCP server is hosted at mcp.railway.com. It lets an agent list and create projects, redeploy services, manage feature flags and hand multi-step work to Railway's own agent, through OAuth or the Railway CLI. - Canonical: https://www.anchorterminal.com/tools/railway-mcp-server - Markdown: https://www.anchorterminal.com/tools/railway-mcp-server.md (~7,800 tokens) - Slim: https://www.anchorterminal.com/tools/railway-mcp-server.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/railway-mcp-server.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade C · 56.7/100 · rank #565 of 842 · #6 in Cloud & infrastructure · not agent-ready · confidence medium** ## Assessment A small hosted server with 11 tools, OAuth grants limited to chosen workspaces and one-hour tokens. Most infrastructure work goes through the `railway-agent` tool, which is billed by model tokens. The hosted server's source and tool schemas are not public, there is no read-only scope, and the status page lists about 25 incidents in 90 days. ## Facts | Field | Value | | --- | --- | | Vendor | Railway Corporation (https://railway.com) | | Kind | MCP server | | Category | Cloud & infrastructure (https://www.anchorterminal.com/categories/infrastructure) | | Transport | Streamable HTTP, stdio | | Endpoint | `https://mcp.railway.com` | | Auth | OAuth · OAuth, either handled by the MCP client or reused from a `railway login` session through the CLI. An unauthenticated request answers 401 with a pointer to the protected-resource metadata, which names the authorisation server at backboard.railway.com and one scope, `workspace:member`. The authorisation server supports the authorisation code grant with PKCE (S256), the device code grant, refresh tokens and dynamic client registration. On the consent screen a person picks which workspaces and projects the client reaches. Access tokens last one hour and refresh tokens rotate. Grants are revoked in the dashboard, and there is no revocation endpoint. Project tokens are refused. | | Pricing | Your plan (Your plan) · The server itself has no charge. Tools act on a Railway workspace and bill under its plan. A new account gets a 30-day trial with a one-time $5 credit and no card, then the Free plan with $1 of usage a month. Hobby is $5 a month and Pro $20 a month, each with the same amount of usage included, and Enterprise is priced by sales. Usage is metered by the second. The `railway-agent` tool runs Railway's own agent, which is billed for the model tokens it uses at Anthropic's published rates with no markup (checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the MCP server docs, the CLI docs, llms.txt, auth.md or the pricing file (checked 2026-10-09). Railway can be provisioned through Stripe's Agentic Provisioning Protocol, which is a separate route and not a payment protocol on the MCP endpoint. | | Licence | Proprietary hosted server under Railway's Terms of Service. The Railway CLI, which carries the stdio proxy and a separate local MCP server, is MIT | | Tools exposed | 11 | | Packages | npm: `@railway/cli` | | MCP registry name | `com.railway/mcp` | | Source | https://github.com/railwayapp/cli | | Docs | https://docs.railway.com/ai/mcp-server | | llms.txt | https://docs.railway.com/llms.txt | | Last release | 2026-10-08 | | npm downloads / week | 426,205 | | Surface graded | The hosted MCP server at https://mcp.railway.com, reached with OAuth from the MCP client or through the `railway mcp` stdio proxy in the Railway CLI (5.44.0 or later). The CLI's local server, `railway mcp local`, and the GraphQL API at https://backboard.railway.com/graphql/v2 are separate surfaces | | Tools | 11 per the docs. `whoami`, `list-projects`, `create-project`, `list-services`, `list-feature-flags`, `get-feature-flag`, `set-feature-flag`, `delete-feature-flag`, `redeploy`, `accept-deploy` and `railway-agent` | | Not in the hosted tool list | Tools for variables, environments, domains, volumes, buckets, templates, logs and metrics. The docs send multi-step work to `railway-agent`, and the local server has 47 tools covering these | | Protocol | Streamable HTTP, run statelessly with no session id per the CLI proxy source. The proxy does not forward server-initiated messages | | Credentials | OAuth authorisation code with PKCE (S256 required), device code grant, dynamic client registration and client ID metadata documents at backboard.railway.com. One resource scope, `workspace:member`. One-hour access tokens, rotating refresh tokens with a one-year life, revocation in the dashboard only | | Rate limits | None stated for the MCP server. The public API allows 100 requests an hour on Free, 1,000 on Hobby and 10,000 on Pro, with 10 a second on Hobby and 50 on Pro, and sends `Retry-After` on 429 | | Audit | Workspace audit logs for admins, exportable through the GraphQL API. Kept 48 hours on Free, Trial and Hobby, 30 days on Pro and 18 months on Enterprise. Actor types are user, Railway staff and Railway system, with no marker for MCP calls found | | Releases | The hosted server shows version 1.0.0 in its server card and the registry and has no public release history. The CLI that carries the proxy reached v5.64.1 on 8 October 2026 | | Certifications | SOC 2 Type II and SOC 3 per the compliance docs, with a HIPAA BAA as a paid add-on. Reports are requested through trust.railway.com | | Status | status.railway.com, built in-house, with components by region and for the dashboard, the API at backboard.railway.com and Railway OAuth login. No component for the MCP server. A JSON feed is at https://api.railwaystatus.com/status | | Sub-processors | The DPA points to a list at trust.railway.com, which was not read, and promises ten days' notice of a new one. The DPA names Google Cloud Platform for infrastructure and the United States as the primary place of processing | | Capabilities | infra.cloud, code.deploy, analytics.flags | | Tags | official, hosted, mcp, oauth, llms-txt, openapi, status-page, soc2, free-tier | | JSON | https://www.anchorterminal.com/api/v1/tools/railway-mcp-server.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 60 | 12.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 56 | 9.1 | | Agent ergonomics | 13% | 16.2 | 59 | 9.6 | | Security & auth | 14% | 17.5 | 65 | 11.4 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 83 | 7.3 | | Transparency & trust (editorial 61, provenance 84) | 7% | 8.8 | 73 | 6.4 | | Negative events | up to −15 | up to −15 | 30 March 2026. A CDN configuration change cached GET responses on about 0.05% of Railway domains for 52 minutes, so pages meant for one user may have been served to another. Railway reverted it, purged the cache and published a report the same day. Fixed and documented, so 4 is deducted (https://blog.railway.com/p/incident-report-march-30-2026-authenticated-user-data-cached). | -4 | | **Total** | | | | **56.7 → C** | ### Why each score - Reliability 60: Scored as a hosted server. status.railway.com is an in-house status page with component history by region and for the API and OAuth login (20). From 11 July to 8 October 2026 it lists about 25 incidents, on a page that says it reports only incidents with wide impact. Most are slow builds and deployments. They include services and databases unavailable for some users in US West on 3 October, API degradation that paused Hobby deployments on 29 September, a five-minute routing failure for all domains on 30 September and a hardware fault in US West on 29 August. Durations are not shown in the history, and the MCP server is not a component (10 of 30). No limit is stated for the MCP server. The public API's limits are published with numbers, 100 to 10,000 requests an hour by plan (8 of 15). The API docs give `Retry-After` on 429, backoff advice and retry rules for mutations, with no idempotency key (10 of 15). A 99.99% SLA is stated for Enterprise, with terms by contract (5 of 10). The docs carry no beta label and the registry entry is 1.0.0, but the April 2026 launch note called it ready for public testing and no later statement was found (7 of 10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 56: The hosted server's source is closed and `tools/list` needs a signed-in client, so no tool schema was read. A server card and a registry entry are public, and the CLI proxy source shows that tools declare their parameters (15 of 25). llms.txt on both sites and a Markdown twin of every docs page (10). The docs name the 11 tools and describe four of them in a line each. The descriptions the server sends were not read (8 of 20). Input types, enums and bounds could not be read (5 of 15). The docs give example prompts and the 401 challenge, and the API docs list error codes. No list of tool errors was found (9 of 15). Railway's changelog is weekly and dated, but the growth from seven tools to 11 has no dated entry found, and the hosted server shows a fixed version 1.0.0 (9 of 15). - Agent ergonomics 59: Eleven tools, one over the ten that earns full marks, with `railway-agent` taking multi-step work in a single call (20 of 25). The three list tools are the only read tools apart from the flag tools. Pagination and size controls could not be read (6 of 20). A missing or expired token answers 401 with a `WWW-Authenticate` challenge, the CLI proxy returns a login hint, and API errors carry a code and a trace id (12 of 20). The docs say destructive tools are marked at the protocol level so clients prompt. Read-only hints were not established, and there is no idempotency key (12 of 20). The CLI proxy fills project context from the linked directory for tools that accept it. Two official SDKs for the platform API were not found (9 of 15). - Security & auth 65: OAuth with PKCE required, dynamic client registration, grants limited to the workspaces and projects a person picks, one-hour access tokens and rotating refresh tokens. Revocation is in the dashboard only, and the MCP resource lists a single scope, `workspace:member` (25 of 30). There is no read-only grant for the hosted server. Destructive tools carry hints that prompt in clients that respect them, and project tokens are refused (10 of 20). `railway-agent` reads logs and configuration, which are untrusted content. The docs tell users to review actions and keep to non-critical environments, with no prompt-injection guidance found (4 of 15). Workspace audit logs record the actor and can be exported through the API, kept 48 hours on Free and Hobby, 30 days on Pro and 18 months on Enterprise. No marker for MCP calls was found (11 of 15). SOC 2 Type II and SOC 3, a HIPAA BAA, a Bugcrowd bounty that is invite-only and public incident reports. No security.txt (15 of 20). - Payments & pricing 40: No x402, MPP or L402 on the server (0). Railway can be provisioned through Stripe's Agentic Provisioning Protocol, which is a separate route and earns nothing here. Plan fees and per-second prices for CPU, memory, volumes and egress are public (20). The trial gives $5 of credit for 30 days with no card, followed by a Free plan with $1 a month (20). Dynamic client registration needs no setup, but a person has to sign in and approve the grant in a browser or with a device code (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 83: The CLI that carries the proxy reached v5.64.1 on 8 October 2026 and Railway's changelog has an entry dated 1 October (30). More than 100 CLI tags in the last 90 days and a weekly changelog (20). GitHub's API refused us for its rate limit, so issue handling was not read. Railway runs a feedback thread for the server on Central Station (10 of 25). The official MCP registry lists `com.railway/mcp` as active under the vendor's domain namespace (15). The CLI has CI, a cargo-audit workflow and a lockfile. The workflow results were not seen (8 of 10). - Transparency & trust 73: The hosted server is closed source under clear terms. The CLI proxy and the local server are MIT (20 of 30). The DPA is published in full. The privacy policy's full text was not read. Audit log and image retention are stated by plan, and nothing was found on what the hosted server or `railway-agent` keeps from a session (18 of 30). The old npm server was deprecated on 23 May 2026 with a shim and a registry notice, and API fields are marked `@deprecated` before removal with no stated period. The terms let Railway suspend or discontinue any part of the Services (10 of 20). The DPA names Google Cloud Platform and the United States, promises ten days' notice of a new sub-processor and points to a list at trust.railway.com that was not read (13 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/railway-mcp-server.md (JSON https://www.anchorterminal.com/fixes/railway-mcp-server.json) ### What we couldn't check - unchecked: the hosted server's tool schemas, descriptions and annotations. The source is closed and `tools/list` needs a signed-in client, so Schema and Agent ergonomics are scored from the docs. - unchecked: the full text of the Privacy Policy. Its Markdown twin is a summary, and the terms forbid scraping pages of the Services, so the HTML page was not read. - unchecked: the sub-processor list at trust.railway.com, for the same reason. - unchecked: GitHub stars and issue handling for railwayapp/cli. GitHub's API refused us for its rate limit. - unchecked: whether the public API's rate limits apply to MCP tool calls, and whether audit logs mark MCP calls. - unchecked: the terms of the Enterprise 99.99% SLA, which are not published. - unchecked: incident durations. The status history lists titles and closing notes without start and end times. - The Terms of Service were read once from the HTML page before the clause against crawling or scraping was seen. After that only Railway's published agent files, Markdown twins, well-known files and the status pages were requested. robots.txt on railway.com, docs.railway.com, status.railway.com and blog.railway.com signals ai-input=yes. This matters before our probes run. - The lead's description (create projects, deploy templates, manage environments, pull variables) comes from the docs' opening line. The hosted tool list has `create-project` and `redeploy` but no template, environment or variable tool. - The launch note of 17 April 2026 called the server ready for public testing. No later statement that it is generally available was found, and the docs carry no beta label. - The registry name is `com.railway/mcp` while Railway's server card says `com.railway/railway`. - `lastRelease` is the date of the CLI tag v5.64.1, which carries the proxy. The hosted server has no dated releases. ### Sources - MCP server docs: (seen 2026-10-09) - `railway mcp` CLI docs: (seen 2026-10-09) - docs llms.txt: (seen 2026-10-09) - site llms.txt: (seen 2026-10-09) - agent setup briefing: (seen 2026-10-09) - authentication guide for agents: (seen 2026-10-09) - remote MCP summary: (seen 2026-10-09) - MCP server card: (seen 2026-10-09) - MCP protected-resource metadata: (seen 2026-10-09) - OAuth authorisation server metadata: (seen 2026-10-09) - OAuth scopes and consent: (seen 2026-10-09) - OAuth login and tokens: (seen 2026-10-09) - public API docs, rate limits, errors and retries: (seen 2026-10-09) - OpenAPI description: (seen 2026-10-09) - Railway Agent docs and its pricing: (seen 2026-10-09) - pricing: (seen 2026-10-09) - plans docs: (seen 2026-10-09) - free trial docs: (seen 2026-10-09) - Stripe provisioning docs: (seen 2026-10-09) - status page: (seen 2026-10-09) - status history: (seen 2026-10-09) - status feed: (seen 2026-10-09) - incident management docs: (seen 2026-10-09) - blog index and full text, incident reports: (seen 2026-10-09) - incident report of 30 March 2026: (seen 2026-10-09) - changelog index: (seen 2026-10-09) - remote MCP launch note: (seen 2026-10-09) - CLI source, MCP proxy, local server, tags and workflows: (seen 2026-10-09) - deprecated npm MCP server: (seen 2026-10-09) - CLI telemetry docs: (seen 2026-10-09) - compliance docs: (seen 2026-10-09) - audit logs docs: (seen 2026-10-09) - bug bounty: (seen 2026-10-09) - enterprise summary and SLA claim: (seen 2026-10-09) - Terms of Service: (seen 2026-10-09) - Privacy Policy summary: (seen 2026-10-09) - Data Processing Addendum: (seen 2026-10-09) - Acceptable Use Policy: (seen 2026-10-09) - MCP registry search: (seen 2026-10-09) - npm weekly downloads for the CLI: (seen 2026-10-09) - RDAP for railway.com: (seen 2026-10-09) ## Who's behind it (provenance 84/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Railway Corporation | 20/20 | | Domain age | railway.com, registered 1996-01-09 (30 years) | 15/15 | | Endpoint on the vendor's domain | mcp.railway.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | status.railway.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The Terms of Service (effective 20 April 2026) are a contract with Railway Corporation under Delaware law and cover the website, products, services and applications. They incorporate the Privacy Policy, and the DPA supplements them. The Markdown twins of the terms and the privacy policy are summaries that name the HTML pages as the binding text. The terms were read once from the HTML page. The privacy policy's full text was not read, because the terms forbid scraping pages of the Services. The MCP server answers at mcp.railway.com and its authorisation server at backboard.railway.com, both railway.com subdomains. railway.com/.well-known/security.txt answered 404. Security reports go to bugbounty@railway.com and an invite-only Bugcrowd programme. RDAP for railway.com gives a registration date of 1996-01-09. The status feed at api.railwaystatus.com is on a second domain of Railway's. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://railway.com/legal/terms), read 2026-10-08. Our reader couldn't read it (the page our reader gets is a short summary that points to the full document, not the document itself). **Privacy policy** (https://railway.com/legal/privacy), read 2026-10-08. Our reader couldn't read it (the page our reader gets is a short summary that points to the full document, not the document itself). ## Live (updated 2026-10-09 10:42 UTC) - Right now: up, HTTP 401, 217 ms, checked 2026-10-09 10:42 UTC (mcp-initialize on `https://mcp.railway.com`, asks for auth) - Uptime 24h 100.0% (33 probes) · 30 days 100.0% (33 probes) · p50 219 ms · p95 297 ms - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/railway-mcp-server.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Free plan | free | per month (plan) | $1 of usage included | | Hobby plan | $5 | per month (plan) | $5 of usage included | | Pro workspace | $20 | per month (plan) | $20 of usage included | | CPU, one vCPU | $20 | per month (plan) | metered by the second | | Memory | $10 | per GB per month | metered by the second | | Volume storage | $0.15 | per GB per month | | | Network egress | $0.05 | per GB of traffic | | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OAuth with PKCE, dynamic client registration and a device code grant. A person picks the workspaces and projects a client reaches. - Access tokens last one hour, refresh tokens rotate, and the CLI route keeps any long-lived credential out of editor configuration. - Eleven tools keep the context cost low, with `railway-agent` taking multi-step work in one call. - The trial needs no card and prices for CPU, memory, volumes and egress are public and metered by the second. - The CLI that carries the proxy had more than 100 tagged releases in 90 days, the latest on 8 October 2026. ## Weaknesses - The hosted server's source and tool schemas are not public, so inputs can only be read after signing in. - The MCP resource lists one scope, `workspace:member`, with no read-only grant. - The docs say the server can deploy templates, manage environments and pull variables, but no hosted tool is named for those. They go through `railway-agent` or the local server. - status.railway.com lists about 25 incidents from 11 July to 8 October 2026, most on builds and deployments. - Railway reported a 52-minute CDN caching error on 30 March 2026 that may have shown one user's pages to another. ## Before you call it (notes for agents) 1. Connect to `https://mcp.railway.com` with OAuth, or run `railway mcp` after `railway login`. Project tokens are refused. 2. Treat `redeploy`, `accept-deploy`, `delete-feature-flag` and `railway-agent` as actions that change production. Confirm the project and environment first. 3. `railway-agent` spends model tokens billed to the workspace. Use the single-purpose tools for listing and redeploying. 4. For variables, domains, volumes, logs or metrics as separate tools, use `railway mcp local`, which has a different tool set. 5. On a 401, follow the `WWW-Authenticate` challenge and run the OAuth flow again. Access tokens expire after one hour. ## Connect Install: ```bash railway mcp install ``` Claude Code: ```bash claude mcp add railway --transport http https://mcp.railway.com ``` MCP client configuration: ```json { "mcpServers": { "railway": { "url": "https://mcp.railway.com" } } } ``` Through letme (picks today, calling later): https://letme.dev/railway-mcp-server. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Render MCP Server | B | 63.6 | 352 | infra.cloud, code.deploy | no | https://www.anchorterminal.com/tools/render-mcp-server.md | | Google Cloud Secret Manager | BB | 76.5 | 29 | infra.cloud | no | https://www.anchorterminal.com/tools/google-secret-manager.md | | Statsig | BB | 72.3 | 104 | analytics.flags | no | https://www.anchorterminal.com/tools/statsig.md | | Terraform MCP Server | BB | 71.9 | 112 | infra.cloud | no | https://www.anchorterminal.com/tools/terraform-mcp.md | | GrowthBook | BB | 70.1 | 155 | analytics.flags | no | https://www.anchorterminal.com/tools/growthbook.md | | LaunchDarkly | B | 69.2 | 185 | analytics.flags | no | https://www.anchorterminal.com/tools/launchdarkly.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The hosted server lists 11 tools in the docs. `whoami`, `list-projects`, `create-project`, `list-services`, four feature flag tools, `redeploy`, `accept-deploy` and `railway-agent` (source: ) - The remote server went live on 17 April 2026 with seven tools, described then as ready for public testing (source: ) - Since CLI 5.44.0, tagged 25 August 2026, `railway mcp` is a stdio proxy to mcp.railway.com that attaches the `railway login` credential to each request (source: ) - The CLI also ships a different local server, `railway mcp local`, with 47 tools in the MIT source for services, variables, domains, volumes, buckets, logs and metrics (source: ) - The hosted server's source is not public. The earlier npm package `@railway/mcp-server` was deprecated on 23 May 2026 and is now a shim that runs `railway mcp` (source: ) - The official MCP registry lists `com.railway/mcp` 1.0.0 as active, published 22 April 2026. Railway's own server card names it `com.railway/railway` (source: ) - The OAuth metadata for the MCP resource lists one resource scope, `workspace:member`. The wider platform has viewer scopes that the MCP resource does not list (source: ) - Railway reported that on 30 March 2026 a CDN change cached responses on about 0.05% of domains for 52 minutes, so pages meant for one user may have been served to another (source: ) - Railway's Terms of Service, effective 20 April 2026, forbid crawling or scraping any page of the Services, while robots.txt on railway.com signals ai-input=yes (source: ) - railway.com/agents.md is written as instructions to AI agents, including an install command to propose to the user. It is recorded here as a fact about the site and was not acted on (source: ) ## Compare - [Azure MCP Server vs Railway MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-railway-mcp-server.md): B 67.7 vs C 56.7 - [Railway MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.md): C 56.7 vs B 63.6 - [Railway MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp.md): C 56.7 vs BB 71.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on railway.com or one of its subdomains, or the README of github.com/railwayapp/cli. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "railway-mcp-server", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Railway MCP Server on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Railway MCP Server on Anchor Terminal](https://www.anchorterminal.com/badges/railway-mcp-server.svg)](https://www.anchorterminal.com/tools/railway-mcp-server) ``` Plain link: ```html Railway MCP Server on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Railway MCP Server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/railway-mcp-server-dark.png - Light: https://www.anchorterminal.com/assets/share/railway-mcp-server-light.png