Index / MCP servers / run.pay

run.pay MCP server

run.pay is an MCP server with 2 tools an agent can call, among them call_service, list_services. It answers at https://runpay-backend-visibility-production.up.railway.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.

Status
Answering
Tools
2
Reliability
10 of 10 checks
Response time
284 ms
Transport
streamable HTTP
Last checked
18 October 2026

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

Description as the publisher wrote it.

The 2 tools run.pay offers

ToolWhat it does
call_serviceCall a service and pay automatically via Stripe per use
Inputs: service_id, agent_id, payload
list_servicesList all available services for purchase on run.pay marketplace
Inputs: category, search

Add run.pay to your AI client

Every block below points at https://runpay-backend-visibility-production.up.railway.app/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http run-pay https://runpay-backend-visibility-production.up.railway.app/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "run-pay": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://runpay-backend-visibility-production.up.railway.app/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "run-pay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "run-pay": {
      "type": "http",
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "run-pay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "run-pay": {
      "serverUrl": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "run-pay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: run.pay
version: 0.0.1
schema: v1
mcpServers:
  - name: run.pay
    type: streamable-http
    url: https://runpay-backend-visibility-production.up.railway.app/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "run-pay": {
      "httpUrl": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "run-pay": {
      "type": "http",
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "run-pay": {
      "url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Frunpay-backend-visibility-production.up.railway.app%2Fmcp&type=streamable_http&id=run-pay&name=run.pay

Is run.pay up right now?

It answered our last check on 18 October 2026 in 284 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to run.pay

Questions about run.pay

How many tools does run.pay have?

2, as returned by the server's own tools/list on 2 September 2026: call_service, list_services.

Is run.pay down?

It answered our last check on 18 October 2026 in 284 ms. Over 10 checks since 4 September 2026 it answered 10.

How do I add run.pay to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://runpay-backend-visibility-production.up.railway.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does run.pay need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.palabrex. Endpoint host: runpay-backend-visibility-production.up.railway.app. ARD identifier: urn:air:io.github.palabrex:mcp:runpay. First indexed 1 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.