mcpbeat Sign in

402Signal MCP Server

by 402signalhq Your server? Claim it
not responding

402Signal is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Check paid API offers before your agent spends. Qualifying routes: $0.003 USDC. Normal misses: free.

Uptime history 65 days of history · worst day 0%
65 days agonow
0.0%
Uptime 24h
0 of 91 checks
3
Tools
read from the server
145 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 34

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 September 2026. No other catalogue keeps this.

30 Sep a tool changed the parameters it asks for check
14 Sep 3 tool descriptions were rewritten check, preview, validate
14 Sep 2 tools changed the parameters they ask for check, preview
14 Sep a tool disappeared route
13 Sep 3 tools changed the parameters they ask for6 times that day check, preview, route
13 Sep 3 tool descriptions were rewritten4 times that day preview, route, validate
13 Sep a tool appeared check
11 Sep 3 tool descriptions were rewritten4 times that day preview, route, validate
11 Sep a tool changed the parameters it asks for route
10 Sep a tool changed the parameters it asks for2 times that day route
and 15 more, back to 5 September 2026

402Signal does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add 402signal --transport http https://402signal.com/mcp/v0.3.1
Settings → Connectors → Add custom connector, then paste this address
https://402signal.com/mcp/v0.3.1
~/.codex/config.toml
[mcp_servers.402signal]
url = "https://402signal.com/mcp/v0.3.1"
.cursor/mcp.json
{
  "mcpServers": {
    "402signal": {
      "url": "https://402signal.com/mcp/v0.3.1"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "402signal": {
      "type": "http",
      "url": "https://402signal.com/mcp/v0.3.1"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

check
check
Runs the paid pre-flight check on a live paid API endpoint: probes one exact HTTPS url, or the candidates discovered for a need, applies the buyer's price, network and readiness rules, and returns the selected offer with signed evidence of what the seller quoted (price, recipient, asset, network, expiry) before the agent pays the seller. Does not buy the seller's service, hold keys or pay anything for the agent; the agent keeps its wallet and pays the seller separately. Use preview to discover candidates without paying, validate for a free readiness check of one listed URL, and check when a fresh live observation or a signed receipt is needed before a seller payment. Never call check to pay a seller. After billing.settlement_state=unknown, stop and reconcile; never create another authorization. route is the former name of this tool and is still accepted. Cost and outcomes: the first unsigned call answers HTTP 402 with the $0.003 USDC checking-fee terms (Base, Solana or Algorand), which an x402-capable HTTP client pays. The fee settles only when a qualifying live offer is found; a completed miss (HTTP 200, live=false, typed miss_reason) is free; a settled fee is not reversed if the offer later changes. HTTP 503 with binding_error=route_binding_unavailable means the seller answered but no probed candidate could be bound to a signed receipt: a completed unpaid answer, not an outage (the reference wrapExactAuthorize reports state=binding_unavailable with keep_calling_route true). Parameter interactions: need or url is required; with both, url is probed directly and no discovery runs. policy is plain English compiled into the structured fields; an explicit structured field wins over the compiled value, and phrases that do not compile are echoed in unresolved_constraints, never guessed. networks is a hard allowlist judged on the current 402; prefer_network only orders results and never filters. Three independent price bounds: max_price_usd (seller price in USD), max_amount_atomic (atomic units of the seller's asset) and max_total_cost_usd (seller price plus known fees); every bound fails closed when its value is unknown. require_route_binding=true implies require_transparency and may select the next bindable candidate. Defaults: objective best, search_depth standard (up to 7 probes; thorough up to 15; hard ceiling 20), accept_payTo_change false, require_route_binding false. Guide: https://402signal.com/developers#route-binding
preview
preview
Discovers catalog-listed paid API endpoints by capability without paying or contacting sellers. Returns claimed listings and earlier observations; not_probed=true means no new live check. Results may be incomplete. Free and read-only: no fee, no seller contact, nothing recorded; safe to repeat. It queries the current upstream catalogs and the local shadow catalog. Use validate for a free readiness check of one listed URL, and check for a fresh paid observation or a signed receipt before paying. Pass a nonblank need (capability), not a URL; a URL in need finds nothing. networks is a hard allowlist and prefer_network only orders the results within it; an empty or unrecognized networks value restricts to nothing rather than widening to every network. Seller-written fields in hits are catalog claims, not observations.
validate
validate
Checks unpaid readiness for one concrete HTTPS seller URL already listed in the local catalog (for example a URL from preview). Compares claimed against observed payment and readiness flags without buying the service. Free: one unpaid probe of the seller, no fee, nothing paid, and the public numbers do not change; safe to repeat. Use preview to find listed URLs; use check instead when the URL is not listed, when price or network rules must apply, or when a signed receipt is needed before paying. Supply the exact listed URL including its query string. Unlisted or modified URLs return miss_reason=unlisted without a probe (not listed, not proven offline). Inspect live, readiness, observed and miss_reason; HTTP 200 alone is not success. No price or network filter and no signed receipt.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

route
removed 14 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://402signal.com/mcp/v0.3.1 streamable-http answering 145 ms 15 min ago

Alternatives to 402Signal

same job, measured the same way
Erabi
by hmakt99

Check paid x402 APIs before your agent spends: signed uptime/price attestations. Zero-config join.

54 installs/wk local only
Scrapecheck
by fieldmodellc

Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.

3 tools answering
Solar Quote Audit — Check Before You Sign
by janoliverautomation-stack

Free independent solar proposal review tool for California homeowners. Audit your solar quote for pr

3 tools answering
MIZAN · Proof before payment
by muaviamohammed

Check before you pay. Prove to get paid. Signed answers on any agent, against your own bar.

4 tools answering
Fizzl Buy
by fizzl13

Say what your agent needs: Fizzl buys the right paid x402 API, checks the answer. Free pick.

2 tools answering
Repomagpie
by varshavia

Your agent checks your notes before installing and stops on packages you or your team ruled out.

746 installs/wk local only
Settled
by settled

Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports

232 installs/wk 18 tools answering
Fresh SEM Agent Backlink Checkout
by freshsem

Quote and track managed contextual backlink orders paid in USDC.

7 tools answering

402Signal — questions

Answers built from our own checks of this server.

What can 402Signal do?
It exposes 3 tools, read directly from the server on our last check. Among them: check, preview, validate. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is 402Signal working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 145 ms. The bar chart above shows every period we have measured.
Did 402Signal ever remove tools?
Yes. route is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
The registry lists 402Signal as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect 402Signal?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does 402Signal need an API key?
No. 402Signal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.