run.pay is an MCP server published by io.github.PalabreX, hosted at runpay-backend-visibility-production.up.railway.app. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including list_services, call_service.
Stripe-native marketplace where AI agents discover and pay per call for API services.
13 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
List all available services for purchase on run.pay marketplace
| Parameter | Type | Description |
|---|---|---|
| search | string | |
| category | string |
{
"name": "list_services",
"description": "List all available services for purchase on run.pay marketplace",
"inputSchema": {
"type": "object",
"properties": {
"search": {
"type": "string"
},
"category": {
"type": "string"
}
}
}
}Call a service and pay automatically via Stripe per use
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Parameter | Type | Description |
|---|---|---|
| payload * | object | |
| agent_id * | string | |
| service_id * | string |
{
"name": "call_service",
"description": "Call a service and pay automatically via Stripe per use",
"inputSchema": {
"type": "object",
"required": [
"service_id",
"agent_id",
"payload"
],
"properties": {
"payload": {
"type": "object"
},
"agent_id": {
"type": "string"
},
"service_id": {
"type": "string"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.