run.pay

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
75%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~113Tokens (tool definitions)
~383 BTypical response size
Minimal attention impact (0.09% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "runpay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}

Remote endpoints

https://runpay-backend-visibility-production.up.railway.app/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢list_services(category, search)

List all available services for purchase on run.pay marketplace

Input Schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string"
    },
    "search": {
      "type": "string"
    }
  }
}
⚪call_service(service_id, agent_id, payload)

Call a service and pay automatically via Stripe per use

Input Schema

{
  "type": "object",
  "properties": {
    "service_id": {
      "type": "string"
    },
    "agent_id": {
      "type": "string"
    },
    "payload": {
      "type": "object"
    }
  },
  "required": [
    "service_id",
    "agent_id",
    "payload"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools