mcp-registry/app.railway.up.payments-intel-production/payments-intel · v0.1.0
As of 2026-10-20 07:04 UTC, the Railway Up Payments Intel Production Payments Intel MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Cited stablecoin rails, corridors, providers, chain and token facts for agents. x402/MPP paid.
Claude Code
claude mcp add --transport http railway-up-payments-intel-production-pay https://payments-intel-production.up.railway.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"railway-up-payments-intel-production-pay": {
"type": "http",
"url": "https://payments-intel-production.up.railway.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Handshake + tools/list takes ~1,557 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.railway.up.payments-intel-production%2Fpayments-intel/fixes
{
"name": "check_address_format",
"description": "Is this address well formed for this chain, and what is its EIP-55 checksummed form? Free: deterministic address format check for EVM chains (EIP-55 checksum: valid, checksummed form, whether the input checksum was correct, all lowercase or all uppercase) and Solana (base58, 32 bytes). No external calls. 60 calls/min per client. Format only; says nothing about who controls an address.",
"inputSchema": {
"type": "object",
"required": [
"chain",
"address"
],
"properties": {
"chain": {
"type": "string",
"description": "Chain id or name: an EVM chain (e.g. base, ethereum, eip155:8453) or solana"
},
"address": {
"type": "string",
"description": "Address to check"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_corridor",
"description": "Who can move money from this currency or stablecoin to that one, in this country, over which rails? Paid ($0.03 USDC): Money-movement routes from one currency or stablecoin to another: corridors providers publish (rails, speed, fee notes, cited), plus on/off-ramp routes inferred from ramp coverage, labelled as inferred. This server holds no wallet and never pays: it returns the HTTP 402 payment requirements (x402 on Base, MPP on Tempo) and the URL https://payments-intel-production.up.railway.app",
"inputSchema": {
"type": "object",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Currency or stablecoin received, e.g. MXN"
},
"from": {
"type": "string",
"description": "Currency or stablecoin sent, e.g. USDC or USD"
},
"country": {
"type": "string",
"description": "Destination ISO alpha-2 country, e.g. MX"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_chain",
"description": "What are the basic facts of this chain (CAIP-2 id, gas token, explorer, x402/MPP settlement, stablecoins)? Paid ($0.001 USDC): Cited chain facts from a prepared dataset: CAIP-2 chain id, gas token, finality class, block explorer, whether x402 and MPP settle there, and stablecoins. Fields not established from a source are the string \"unknown\". Unknown chains and malformed input return 404/400 and are never charged. This server holds no wallet and never pays: it returns the HTTP 402 payment requir",
"inputSchema": {
"type": "object",
"required": [
"chain"
],
"properties": {
"chain": {
"type": "string",
"description": "Chain slug, name or CAIP-2 id, e.g. base, solana, eip155:8453"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.railway.up.payments-intel-production/payments-intel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.railway.up.payments-intel-production/payments-intel"}) over MCP.
search_providers ~314 tokensstablecoin_rails ~293 tokensget_token ~252 tokensfind_corridor ~241 tokensget_chain ~198 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.railway.up.payments-intel-production%2Fpayments-intel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.railway.up.payments-intel-production%2Fpayments-intel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.railway.up.payments-intel-production%2Fpayments-intel.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.railway.up.payments-intel-production%2Fpayments-intel.svg :target: https://glimind.com/server/mcp-registry%2Fapp.railway.up.payments-intel-production%2Fpayments-intel?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ebe97438da5b2f1b…, first seen 2026-10-17, included at leaf 10829 of 31,414. Version history · verify what your client received.
Compare: most reliable other servers · most reliable finance servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 07:04 UTC, the Railway Up Payments Intel Production Payments Intel MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Railway Up Payments Intel Production Payments Intel MCP server advertises 8 tools, including check_address_format, find_corridor, get_chain, get_examples, get_provider.
Point your MCP client at this streamable-http endpoint: https://payments-intel-production.up.railway.app/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.