Finance · Remote MCP server
run.pay
Stripe-native marketplace where AI agents discover and pay per call for API services.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.PalabreX/runpay- Version
- 1.0.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-06-28
- Updated
- 2026-06-28
- Publisher
- PalabreX (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/PalabreX) · how
- Listed under
- Stripe MCP servers
- Website
- getrunpay.com
- Repository
- github.com/PalabreX/runpay-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://runpay-backend-visibility-production.up.railway.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- runpay-marketplace 1.0.0 · protocol 2024-11-05
- Tools discovered
- 2:
list_services,call_service - Checked on
- 2026-10-05
How to connect run.pay
run.pay is a remote MCP server: there is nothing to install. Its endpoint is https://runpay-backend-visibility-production.up.railway.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| Rubin ExchangeRubin: self-custody DEX for crypto perpetuals & spot - trade, read positions, orders, balances. | Remote · HTTPLive check: ✓ handshake |
| Rubric MCPAttested evidence tools for AI agents: sanctions screening, agent/wallet records, paid via x402. | Local · stdio |
| Rug Munch MCPCrypto risk intelligence: 19 tools for rug pull detection, AI forensics, and token analysis. | Local · stdio |
| Rugcheck AiSolana token safety for AI agents - rug-pull, honeypot & Token-2022 trap detection before you buy. | Remote · HTTPLive check: ✗ no handshake |
| RunOnProof - Payment Decision and Agent IDFree agent identity and signed US supplier-payment decisions. Inspect first; verify portable proof. | Remote · HTTPLive check: ✗ no handshake |
| RustChain MCPMCP server for RustChain blockchain, BoTTube video, and Beacon agent messaging. | Local · stdio |
| Rustok WalletSelf-custody Ethereum agent wallet (MCP/stdio). Keys stay in a local Docker volume. | Local · stdio |
| Rustok WalletSelf-custody Ethereum Agent Wallet. All chains enabled by default. User assumes all risks. | Local · stdio |