io.github.89rat/x402-checks
REMOTE · API.CODE402.DEV
Machine-payable deterministic identifier checks + signed XDR-1 receipts for agents.
Available components
Last scanned (8 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
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
- 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 4 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
- 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 Usability68
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 543 tokens (~90/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 10 days we've observed: 24 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 16 Oct 26 −18
- Authorization: partial → unverified ▼ security
- Stability: 0.27 → fail ▼ security
- A breaking change shipped without a version bump: still 1.3.0 ▼ security
- Tool “balance_check” was removed ▼ security
- Tool “batch_validate” was removed ▼ security
- Tool “block_info” was removed ▼ security
- Tool “calculate_fx_savings” was removed ▼ security
- Tool “check_price” was removed ▼ security
- Tool “clean_markdown_scraper” was removed ▼ security
- Tool “context_distill” was removed ▼ security
- Tool “crypto_ticker” was removed ▼ security
- Tool “erc20_balance” was removed ▼ security
- Tool “fx_spot_price_oracle” was removed ▼ security
- Tool “gstin_check” was removed ▼ security
- Tool “iban_check” was removed ▼ security
- Tool “ifsc_check” was removed ▼ security
- Tool “india_supplier_check” was removed ▼ security
- Tool “instant_json_schema_verifier” was removed ▼ security
- Tool “lei_check” was removed ▼ security
- Tool “pre_disbursement_guard” was removed ▼ security
- Tool “receipt_verify” was removed ▼ security
- Tool “sanctions_address_screen” was removed ▼ security
- Tool “swift_bic_check” was removed ▼ security
- Tool “token_contract_risk” was removed ▼ security
- Tool “tx_activity” was removed ▼ security
- Tool “vat_mod97_check” was removed ▼ security
- Tool “vendor_onboarding_pack” was removed ▼ security
- Tool coverage: 100% → 0% ▼ functional
- Schema quality: pass → fail ▼ functional
- Schema quality: 2258 → 543 ▲ functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → fair functional
- New resource “Complete Validator Catalog (65+ Global Formats)” functional
- New resource “XDR-1 182-Byte Binary Preimage & 65B Ed25519 Passport Specification” functional
- New tool “reconcile” functional
- New tool “screen_entity” functional
- New tool “solvency_check” functional
- New tool “verify_id” functional
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “sanctions_address_screen” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.10 ▲ functional
- Tool “sanctions_address_screen” changed its title: OFAC SDN & Sanctions List Edge Screener → Address Snapshot & Operator Policy Comparison cosmetic
- 7 Oct 26 77
First indexed and scored.
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 17 Oct 2026 · Probed https://api.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 | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ab6b55814698f5a40e70829bb0d2ed51 |
| SANs: code402.dev, api.code402.dev, *.api.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 api.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 |
| x-frame-options | SAMEORIGIN |
| 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://api.code402.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.code402.dev/mcp | HTTPS enforced | 301 | https://api.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 →
reconcile ~64
reconcile=reconcile_commerce(order:obj!,payments:arr!,delivery:obj?,certify:bool?)->XDR1ExceptionReport
| Name | Type | Req | Description |
|---|---|---|---|
| certify | boolean | – | – |
| delivery | object | – | – |
| order | object | yes | – |
| payments | array | yes | – |
No output schema declared.
No examples provided.
screen_entity ~56
screen_entity=screen_sanctions_exact(entity:str!,jurisdiction:str?,wallet:str?)->XDR1SanctionsVerdict
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| jurisdiction | string | – | – |
| wallet | string | – | – |
No output schema declared.
No examples provided.
solvency_check ~66
solvency_check=balance_check(wallet:str!,asset:enum[USDC|EURC|ETH]?,min_minor:str?)->XDR1SolvencyProof
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| min_minor | string | – | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
verify_id ~85
verify_id=verify_identifier(kind:enum[iban|lei|vat|gstin|ein|abn|duns|bic|isin|npi|uk_crn|eu_eori|other]!,id:str!,cc:str?)->XDR1Receipt
| Name | Type | Req | Description |
|---|---|---|---|
| cc | string | – | – |
| id | string | yes | – |
| kind | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.89rat/x402-checks MCP server?
io.github.89rat/x402-checks is a hosted endpoint at https://api.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 · api.code402.dev
claude mcp add --transport http 89rat-x402-checks 'https://api.code402.dev/mcp'
What is the io.github.89rat/x402-checks MCP server?
io.github.89rat/x402-checks is an MCP server listed in the public MCP registry as io.github.89rat/x402-checks. Machine-payable deterministic identifier checks + signed XDR-1 receipts for agents. This page covers its hosted endpoint (https://api.code402.dev/mcp).
Is the io.github.89rat/x402-checks MCP server safe to use?
io.github.89rat/x402-checks scores 63 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/x402-checks MCP server expose?
io.github.89rat/x402-checks exposes 4 tools: verify_id, reconcile, screen_entity, solvency_check. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.
Does the io.github.89rat/x402-checks MCP server require authentication?
No. We connected to io.github.89rat/x402-checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.89rat/x402-checks MCP server still maintained?
io.github.89rat/x402-checks is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.