# Stablecoin rails, corridors and payment provider data (remote · payments-intel-production.up.railway.app)

Cited stablecoin rails, corridors, providers, chain and token facts for agents. x402/MPP paid.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `payments-intel-production.up.railway.app`: 66/100 (this document), [markdown](https://verifymcp.io/servers/app-railway-up-payments-intel-production-payments-intel/payments-intel-production.md), [page](https://verifymcp.io/servers/app-railway-up-payments-intel-production-payments-intel/payments-intel-production)

## Channel facts

- Endpoint: `https://payments-intel-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1645 tokens (~205/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Stablecoin rails, corridors and payment provider data MCP server?

Stablecoin rails, corridors and payment provider data is a hosted endpoint at https://payments-intel-production.up.railway.app/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 app-railway-up-payments-intel-production-payment 'https://payments-intel-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-railway-up-payments-intel-production-payment": {
      "url": "https://payments-intel-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-railway-up-payments-intel-production-payment": {
      "type": "http",
      "url": "https://payments-intel-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-railway-up-payments-intel-production-payment]
url = "https://payments-intel-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-railway-up-payments-intel-production-payment": {
      "type": "remote",
      "url": "https://payments-intel-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-railway-up-payments-intel-production-payment --url 'https://payments-intel-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-railway-up-payments-intel-production-payment:
    url: "https://payments-intel-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-railway-up-payments-intel-production-payment": {
      "Transport": "http",
      "Url": "https://payments-intel-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-railway-up-payments-intel-production-payment -t streamable-http -u 'https://payments-intel-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-railway-up-payments-intel-production-payment": {
      "type": "http",
      "url": "https://payments-intel-production.up.railway.app/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-10-21 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, 0)

- [functional regression] Schema quality: 1353 → 1616
- [functional] New tool “get_token”

### 2026-10-13 (score 63, +1)

- [functional improvement] Schema quality: 232 → 193
- [functional] New tool “check_address_format”
- [functional] New tool “get_chain”
- [functional] New tool “get_examples”

### 2026-10-12 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (8)

### `search_providers` (~250 tokens)

Which payment or stablecoin providers support this asset, chain, country or service? Free: search payment and stablecoin providers by category, asset, chain, ramp country or service. Returns compact cards (no citations); use get_provider for the full cited record. 50 calls/day per client.

Input parameters:

- `asset` (string): Stablecoin ticker, e.g. USDC, EURC, USDT, PYUSD
- `category` (string): card_acquiring, orchestration, merchant_of_record, payouts, fx, baas_issuing, open_banking, stablecoin_issuer, stablecoin_infra, onoff_ramp, custody_wallets, agentic_payments
- `chain` (string): Chain, e.g. base, ethereum, solana, tron, polygon
- `country` (string): ISO 3166-1 alpha-2 country for on/off-ramp coverage, e.g. MX
- `q` (string): Name search, e.g. 'bridge'
- `service` (string): issuance, mint_redeem, on_ramp, off_ramp, payouts, acceptance, settlement, custody, wallets, orchestration, fx, cards

### `get_provider` (~150 tokens)

What exactly does this provider support, where is it licensed and what does it charge? Paid ($0.01 USDC): Full cited record for one provider: stablecoin rails, corridors, licences, published fees, coverage, developer and agent-payment support. Every fact has source URL, retrieval date, quote and confidence. 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/v1/provider. Pay with your own x402/MPP client and retry that URL.

Input parameters:

- `id` (string, required): Provider id from search_providers, e.g. circle

### `stablecoin_rails` (~274 tokens)

Who can on-ramp, off-ramp, issue or settle this stablecoin, on which chain, in which country? Paid ($0.01 USDC): Stablecoin rails by asset, chain, country and service, with the cited stablecoin block for each matching provider (assets, chains, ramp countries, fiat rails, custody model). Country matches say whether the country is listed or only covered by a 'global' claim. 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/v1/stablecoin-rails. Pay with your own x402/MPP client and retry that URL.

Input parameters:

- `asset` (string): Stablecoin ticker, e.g. USDC, EURC, USDT, PYUSD
- `chain` (string): Chain, e.g. base, ethereum, solana, tron, polygon
- `country` (string): ISO 3166-1 alpha-2 country for on/off-ramp coverage, e.g. MX
- `service` (string): issuance, mint_redeem, on_ramp, off_ramp, payouts, acceptance, settlement, custody, wallets, orchestration, fx, cards

### `find_corridor` (~198 tokens)

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/v1/corridor. Pay with your own x402/MPP client and retry that URL.

Input parameters:

- `country` (string): Destination ISO alpha-2 country, e.g. MX
- `from` (string, required): Currency or stablecoin sent, e.g. USDC or USD
- `to` (string, required): Currency or stablecoin received, e.g. MXN

### `get_examples` (~75 tokens)

What do the paid endpoints return, and what do they cost? Free: prices and paths of every paid endpoint, plus a full example response for GET /v1/provider taken verbatim from a real record, labelled as an example with its last-verified date. Use it to see the shape and depth of paid data before paying.

### `check_address_format` (~143 tokens)

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.

Input parameters:

- `address` (string, required): Address to check
- `chain` (string, required): Chain id or name: an EVM chain (e.g. base, ethereum, eip155:8453) or solana

### `get_chain` (~204 tokens)

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 requirements (x402 on Base, MPP on Tempo) and the URL https://payments-intel-production.up.railway.app/v1/chain. Pay with your own x402/MPP client and retry that URL.

Input parameters:

- `chain` (string, required): Chain slug, name or CAIP-2 id, e.g. base, solana, eip155:8453

### `get_token` (~263 tokens)

What are the symbol, name, decimals, contract address and issuer of this stablecoin on this chain? Paid ($0.001 USDC): Cited stablecoin token facts from a prepared dataset (USDC, EURC, USDT, PYUSD, DAI on the chains /v1/chain covers, where a permissively licensed source lists them): symbol, name, decimals, contract address, chain, issuer, each with a source citation and license. Fields not established from a source are the string "unknown". Malformed input and tokens not in the dataset return 400/404 and are never charged. 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/v1/token. Pay with your own x402/MPP client and retry that URL.

Input parameters:

- `address` (string): Token contract / mint address (give address or symbol)
- `chain` (string, required): Chain slug, name or CAIP-2 id, e.g. base, solana, eip155:8453
- `symbol` (string): Stablecoin ticker, e.g. USDC (give symbol or address)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-railway-up-payments-intel-production-payments-intel/payments-intel-production#diagnostics

## Score history

- 2026-10-22: 66
- 2026-10-21: 66
- 2026-10-20: 65
- 2026-10-19: 65
- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 63
- 2026-10-12: 62
- 2026-10-10: 61
- 2026-10-09: 61

## Common questions

### What is the Stablecoin rails, corridors and payment provider data MCP server?

Stablecoin rails, corridors and payment provider data is an MCP server listed in the public MCP registry as app.railway.up.payments-intel-production/payments-intel. Cited stablecoin rails, corridors, providers, chain and token facts for agents. x402/MPP paid. This page covers its hosted endpoint (https://payments-intel-production.up.railway.app/mcp).

### Is the Stablecoin rails, corridors and payment provider data MCP server safe to use?

Stablecoin rails, corridors and payment provider data scores 66 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 Stablecoin rails, corridors and payment provider data MCP server expose?

Stablecoin rails, corridors and payment provider data exposes 8 tools: search_providers, get_provider, stablecoin_rails, find_corridor, get_examples, and 3 more. Their descriptions and schemas cost roughly 1,557 tokens of context every time the server is loaded.

### Does the Stablecoin rails, corridors and payment provider data MCP server require authentication?

No. We connected to Stablecoin rails, corridors and payment provider data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Stablecoin rails, corridors and payment provider data MCP server still maintained?

Stablecoin rails, corridors and payment provider data is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://payments-intel-production.up.railway.app/mcp
- Website: https://payments-intel-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-railway-up-payments-intel-production-payments-intel/payments-intel-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-railway-up-payments-intel-production-payments-intel/payments-intel-production.json
- HTML version of this page: https://verifymcp.io/servers/app-railway-up-payments-intel-production-payments-intel/payments-intel-production