mcpbeat

run.pay MCP Server

io.github.PalabreX/runpay
answering

run.pay is answering right now. Last checked 14 min ago. It exposes 2 tools. Last commit 28 Jun 2026.

Stripe-native marketplace where AI agents discover and pay per call for API services.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
364 ms
Response time
average over 24h
1
Stars
last commit 28 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add runpay --transport http https://runpay-backend-visibility-production.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "runpay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.runpay]
url = "https://runpay-backend-visibility-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "runpay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "runpay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

call
call_service
Call a service and pay automatically via Stripe per use
services
list_services
List all available services for purchase on run.pay marketplace

Endpoints

URLTransportStateLatencyChecked
https://runpay-backend-visibility-production.up.railway.app/mcp streamable-http answering 346 ms 14 min ago

run.pay — questions

Answers built from our own checks of this server.

What can run.pay do?
It exposes 2 tools, read directly from the server on our last check. Among them: call_service, list_services. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is run.pay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 364 ms. The bar chart above shows every period we have measured.
How do I connect run.pay?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does run.pay need an API key?
No. run.pay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is run.pay?
It answers our handshake in 364 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is run.pay open source?
Yes — it is published under the MIT licence, written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.