Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Run402

REMOTE · MCP.RUN402.COM · 2 COMPONENTS · SCANNED SEP 20

x402 pay-per-call infra for agents: $0.03 image generation, Postgres, auth, storage, functions.

0 this week 80 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 331 tokens (~82/item across 4 items; 4 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Run402 MCP server?

Run402 is a hosted endpoint at https://mcp.run402.com/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 · mcp.run402.com

# add to Claude Code
claude mcp add --transport http com-run402-mcp 'https://mcp.run402.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-run402-mcp": {
      "url": "https://mcp.run402.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-run402-mcp": {
      "type": "http",
      "url": "https://mcp.run402.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-run402-mcp]
url = "https://mcp.run402.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-run402-mcp": {
      "type": "remote",
      "url": "https://mcp.run402.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-run402-mcp --url 'https://mcp.run402.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-run402-mcp:
    url: "https://mcp.run402.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-run402-mcp": {
      "Transport": "http",
      "Url": "https://mcp.run402.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-run402-mcp -t streamable-http -u 'https://mcp.run402.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-run402-mcp": {
      "type": "http",
      "url": "https://mcp.run402.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Aug 26 +1
    • 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
  • 23 Aug 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.

  • 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
  • 31 Jul 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
  • 30 Jul 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
  • 27 Jul 26 0
    • Stability: unverified → 0.03 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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://mcp.run402.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.run402.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 28 May 2026 11 Dec 2026 RSA 2048 SHA256-RSA 5d061d35120880e42ffaab1134a7679
SANs: *.run402.com, run402.app, *.run402.app
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.run402.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
run402.com. 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
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'
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://mcp.run402.com/mcp Verified 200
http (plaintext) http://mcp.run402.com/mcp HTTPS enforced 301 https://mcp.run402.com/mcp
MCP tools · 4 exposed · ~282 tokens

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 →

Tool Tokens
experiment_scoreboard ~56

Live state of run402's public demand experiment: on-chain USDC receipts to the seller wallet since launch (2026-07-20), split internal vs external, plus the claims wall. Chain-verified, honest by construction.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run402_quickstart ~65

How an agent gets a Postgres database, static site, serverless functions, storage and email on run402 with no signup — paid per-use with x402 USDC on Base. Returns the 60-second start, key URLs, and the free-testnet path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_wall_claim ~104

Prove your agent paid an x402 endpoint on run402: submit the Base-mainnet tx hash of a USDC payment (>= $0.03 to the run402 seller) and join the public claims wall at scoreboard.run402.com/gallery. Free; verified on-chain before it lands.

NameTypeReqDescription
promptstringoptional: what you generated/bought
tx_hashstringyes0x-prefixed 32-byte tx hash on Base mainnet

No output schema declared.

No examples provided.

x402_price_check ~57

Inspect any https URL for x402 pricing: performs an unpaid request and decodes the 402 challenge (price, network, asset, recipient). Free — no payment is made.

NameTypeReqDescription
urlstringyeshttps URL to probe

No output schema declared.

No examples provided.

Common questions

What is the Run402 MCP server?

Run402 is an MCP server listed in the public MCP registry as com.run402/mcp. x402 pay-per-call infra for agents: $0.03 image generation, Postgres, auth, storage, functions. This page covers its hosted endpoint (https://mcp.run402.com/mcp).

Is the Run402 MCP server safe to use?

Run402 scores 80 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 Run402 MCP server expose?

Run402 exposes 4 tools: run402_quickstart, x402_price_check, submit_wall_claim, experiment_scoreboard. Their descriptions and schemas cost roughly 282 tokens of context every time the server is loaded.

Does the Run402 MCP server require authentication?

No. We connected to Run402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Run402 MCP server still maintained?

Run402 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.