run.pay
REMOTE · RUNPAY-BACKEND-VISIBILITY-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 20
Stripe-native marketplace where AI agents discover and pay per call for API services.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 75 tokens (~37/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the run.pay MCP server?
run.pay is a hosted endpoint at https://runpay-backend-visibility-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · runpay-backend-visibility-production.up.railway.app
claude mcp add --transport http palabrex-runpay 'https://runpay-backend-visibility-production.up.railway.app/mcp'
{
"mcpServers": {
"palabrex-runpay": {
"url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
}
}
} {
"servers": {
"palabrex-runpay": {
"type": "http",
"url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
}
}
} [mcp_servers.palabrex-runpay] url = "https://runpay-backend-visibility-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"palabrex-runpay": {
"type": "remote",
"url": "https://runpay-backend-visibility-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add palabrex-runpay --url 'https://runpay-backend-visibility-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
palabrex-runpay:
url: "https://runpay-backend-visibility-production.up.railway.app/mcp" {
"McpServers": {
"palabrex-runpay": {
"Transport": "http",
"Url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
}
}
} assistant mcp add palabrex-runpay -t streamable-http -u 'https://runpay-backend-visibility-production.up.railway.app/mcp'
{
"mcpServers": {
"palabrex-runpay": {
"type": "http",
"url": "https://runpay-backend-visibility-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 −2
- Stability: pass → 0.87 functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://runpay-backend-visibility-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of runpay-backend-visibility-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://runpay-backend-visibility-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://runpay-backend-visibility-production.up.railway.app/mcp | HTTPS enforced | 301 | https://runpay-backend-visibility-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_service ~42
Call a service and pay automatically via Stripe per use
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| payload | object | yes | – |
| service_id | string | yes | – |
No output schema declared.
No examples provided.
list_services ~33
List all available services for purchase on run.pay marketplace
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
What is the run.pay MCP server?
run.pay is an MCP server listed in the public MCP registry as io.github.PalabreX/runpay. Stripe-native marketplace where AI agents discover and pay per call for API services. This page covers its hosted endpoint (https://runpay-backend-visibility-production.up.railway.app/mcp).
Is the run.pay MCP server safe to use?
run.pay scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the run.pay MCP server expose?
run.pay exposes 2 tools: list_services, call_service. Their descriptions and schemas cost roughly 75 tokens of context every time the server is loaded.
Does the run.pay MCP server require authentication?
No. We connected to run.pay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the run.pay MCP server still maintained?
run.pay is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.