io.github.89rat/code402
REMOTE · MCP.CODE402.DEV · SCANNED SEP 20
Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1276 tokens (~127/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "code402_probe_endpoint" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.89rat/code402 MCP server?
io.github.89rat/code402 is a hosted endpoint at https://mcp.code402.dev/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.code402.dev
claude mcp add --transport http 89rat-code402 'https://mcp.code402.dev/mcp'
{
"mcpServers": {
"89rat-code402": {
"url": "https://mcp.code402.dev/mcp"
}
}
} {
"servers": {
"89rat-code402": {
"type": "http",
"url": "https://mcp.code402.dev/mcp"
}
}
} [mcp_servers.89rat-code402] url = "https://mcp.code402.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"89rat-code402": {
"type": "remote",
"url": "https://mcp.code402.dev/mcp",
"enabled": true
}
}
} openclaw mcp add 89rat-code402 --url 'https://mcp.code402.dev/mcp' --transport streamable-http
mcp_servers:
89rat-code402:
url: "https://mcp.code402.dev/mcp" {
"McpServers": {
"89rat-code402": {
"Transport": "http",
"Url": "https://mcp.code402.dev/mcp"
}
}
} assistant mcp add 89rat-code402 -t streamable-http -u 'https://mcp.code402.dev/mcp'
{
"mcpServers": {
"89rat-code402": {
"type": "http",
"url": "https://mcp.code402.dev/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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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.code402.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=code402.dev | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | add79273876816590ea13211342db733 |
| SANs: code402.dev, mcp.code402.dev, *.mcp.code402.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.code402.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| code402.dev. | 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=15552000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.code402.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.code402.dev/mcp | HTTPS enforced | 301 | https://mcp.code402.dev/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 →
code402_create_listing List an API for sale ~177
Create or update a paid listing for a registered seller: POST /v1/sellers/{sellerId}/services with { serviceId, upstream_url, price_usd, method?, description? }. The gateway then serves the listing at /s/{sellerId}/{serviceId} behind an x402 paywall paying the seller's wallet directly. Returns { listing, paid_endpoint }.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What buyers get for the price |
| method | string | – | HTTP method of the upstream (default GET) |
| price_usd | string | yes | Price per call, e.g. '$0.05' |
| sellerId | string | yes | Registered seller slug |
| serviceId | string | yes | Listing slug, e.g. 'lookup' |
| upstream_url | string | yes | Public https URL of the API being sold |
No output schema declared.
No examples provided.
code402_gateway_health Gateway health & network ~47
Check the code402 gateway's /healthz: returns { status, service, network } where network is the settlement chain currently configured (e.g. base-sepolia or base).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
code402_get_agent_reputation Get an agent's signed reputation credential ~124
Fetch an agent's tamper-evident reputation credential from the code402 Atlas rail: GET /v1/agent/{agent_id}/reputation. The credential is an HMAC-signed, expiring (10-minute TTL) bundle over a hash-chained outcome ledger — settled_ok, settled_fail, distinct_hosts, volume_units, reputation_score — verifiable without any shared secret via POST /v1/reputation/verify. Sellers use this to price counterparty risk before serving a new agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Atlas agent id |
No output schema declared.
No examples provided.
code402_get_seller_analytics Seller analytics ~73
Fetch a seller's own settlement analytics (free): GET /v1/sellers/{sellerId}/analytics. Returns { total_settled_calls, gross_usd, unique_buyers, by_service: [{ service_id, calls }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| sellerId | string | yes | Registered seller slug |
No output schema declared.
No examples provided.
code402_get_seller_invoice Seller take-rate invoice ~115
Compute a seller's platform-fee invoice from settled receipts: GET /v1/sellers/{sellerId}/invoice?since={unix_ms}. Returns { tier, transactions, gross_usdc_units, platform_fee_usdc_units, seller_net_usdc_units, fee_bps }. Amounts are integer USDC base units (6 decimals).
| Name | Type | Req | Description |
|---|---|---|---|
| sellerId | string | yes | Registered seller slug |
| since | integer | – | Unix ms timestamp; only receipts at/after this are invoiced (default 0) |
No output schema declared.
No examples provided.
code402_get_service Get one service ~79
Fetch a single service from the code402 storefront by its serviceId (as returned by code402_list_services). Returns the same service shape as code402_list_services, or an error naming close matches when the id is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | Exact serviceId, e.g. 'weather' or 'acme-lookup' |
No output schema declared.
No examples provided.
code402_list_services List machine-payable services ~224
List services on the code402 gateway storefront (GET /v1/services): first-party APIs and third-party seller listings, each with method, URL, USDC price, and network. No account or API key exists or is needed anywhere on the gateway — paid services are accountless, priced per call via x402. Paying for a service requires an x402-capable HTTP client with the buyer's own wallet — this tool only discovers. Returns { total, count, offset, has_more, next_offset?, services: [{ serviceId, name, description, method, url, price, price_usdc_units, network }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Token-saving mode: returns one terse line per service (serviceId | price | method | url) instead of full objects. Use for large catalogs. |
| limit | integer | – | Maximum services to return (default 20) |
| offset | integer | – | Services to skip (pagination, default 0) |
| query | string | – | Case-insensitive substring filter on serviceId, name, and description |
No output schema declared.
No examples provided.
code402_probe_endpoint Probe a URL for x402 payment terms ~98
Send an unpaid GET to any public https URL and report whether it answers with a valid x402 402 challenge, plus normalized terms { scheme, network, amount (USDC base units), price (dollars), payTo, asset }. Use before budgeting a payment or to liveness-check a listing. No payment is ever sent. Private/internal addresses are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public https URL of the endpoint to probe |
No output schema declared.
No examples provided.
code402_register_seller Register a seller ~182
Register a seller on the code402 gateway (or update its name — the payout wallet is immutable once set; re-binding requires EIP-191 proof): POST /v1/sellers with { id, wallet, name }. Payments for the seller's listings settle directly to this wallet (non-custodial). Registration is free; fees are 0.099% of settled volume, invoiced monthly against receipts (accrued until $9). Pro is $9/mo at 0% take. Returns { sellerId, wallet, storefront }. Prove wallet ownership later via the gateway's EIP-191 verify-challenge flow.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Seller slug, e.g. 'acme' |
| name | string | yes | Human-readable seller name |
| wallet | string | yes | EVM wallet that receives USDC payments |
No output schema declared.
No examples provided.
code402_trust_check Trust-check an endpoint or domain ~157
Query the code402 Atlas index for measured trust evidence on an endpoint or domain: probe-verified liveness (probedAlive), evidence tier (probe vs asserted), and ready-to-pay settlement terms (payTo, asset, CAIP-2 network, integer USDC amountUnits) when measured. Use before letting an agent pay any endpoint. Verified evidence is measured by probes, never self-reported. Returns { count, results: [{ title, url, probedAlive, evidence, settlement? }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10) |
| q | string | yes | Search query — domain, URL, or service name, e.g. 'weather' or 'api.acme.com' |
No output schema declared.
No examples provided.
What is the io.github.89rat/code402 MCP server?
io.github.89rat/code402 is an MCP server listed in the public MCP registry as io.github.89rat/code402. Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial. This page covers its hosted endpoint (https://mcp.code402.dev/mcp).
Is the io.github.89rat/code402 MCP server safe to use?
io.github.89rat/code402 scores 87 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 io.github.89rat/code402 MCP server expose?
io.github.89rat/code402 exposes 10 tools: code402_list_services, code402_get_service, code402_probe_endpoint, code402_gateway_health, code402_register_seller, and 5 more. Their descriptions and schemas cost roughly 1,276 tokens of context every time the server is loaded.
Does the io.github.89rat/code402 MCP server require authentication?
No. We connected to io.github.89rat/code402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.89rat/code402 MCP server still maintained?
io.github.89rat/code402 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.