# io.github.89rat/x402-checks (remote · api.code402.dev)

Machine-payable deterministic identifier checks + signed XDR-1 receipts for agents.

- Trust score: 63/100 (medium)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `api.code402.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/89rat-x402-checks/api.md), [page](https://verifymcp.io/servers/89rat-x402-checks/api)

## Channel facts

- Endpoint: `https://api.code402.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 543 tokens (~90/item across 6 items; 4 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 10 days we've observed: 24 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http 89rat-x402-checks 'https://api.code402.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "89rat-x402-checks": {
      "url": "https://api.code402.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "89rat-x402-checks": {
      "type": "http",
      "url": "https://api.code402.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.89rat-x402-checks]
url = "https://api.code402.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "89rat-x402-checks": {
      "type": "remote",
      "url": "https://api.code402.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 89rat-x402-checks --url 'https://api.code402.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  89rat-x402-checks:
    url: "https://api.code402.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "89rat-x402-checks": {
      "Transport": "http",
      "Url": "https://api.code402.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 89rat-x402-checks -t streamable-http -u 'https://api.code402.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "89rat-x402-checks": {
      "type": "http",
      "url": "https://api.code402.dev/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 63, −18)

- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.27 → fail
- [security regression] A breaking change shipped without a version bump: still 1.3.0
- [security regression] Tool “balance_check” was removed
- [security regression] Tool “batch_validate” was removed
- [security regression] Tool “block_info” was removed
- [security regression] Tool “calculate_fx_savings” was removed
- [security regression] Tool “check_price” was removed
- [security regression] Tool “clean_markdown_scraper” was removed
- [security regression] Tool “context_distill” was removed
- [security regression] Tool “crypto_ticker” was removed
- [security regression] Tool “erc20_balance” was removed
- [security regression] Tool “fx_spot_price_oracle” was removed
- [security regression] Tool “gstin_check” was removed
- [security regression] Tool “iban_check” was removed
- [security regression] Tool “ifsc_check” was removed
- [security regression] Tool “india_supplier_check” was removed
- [security regression] Tool “instant_json_schema_verifier” was removed
- [security regression] Tool “lei_check” was removed
- [security regression] Tool “pre_disbursement_guard” was removed
- [security regression] Tool “receipt_verify” was removed
- [security regression] Tool “sanctions_address_screen” was removed
- [security regression] Tool “swift_bic_check” was removed
- [security regression] Tool “token_contract_risk” was removed
- [security regression] Tool “tx_activity” was removed
- [security regression] Tool “vat_mod97_check” was removed
- [security regression] Tool “vendor_onboarding_pack” was removed
- [functional regression] Tool coverage: 100% → 0%
- [functional regression] Schema quality: pass → fail
- [functional improvement] 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”

### 2026-10-15 (score 81, +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.

### 2026-10-13 (score 80, +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.

### 2026-10-12 (score 79, +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.

### 2026-10-10 (score 78, +1)

- [security] 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
- [functional improvement] Stability: unverified → 0.10
- [cosmetic] Tool “sanctions_address_screen” changed its title: OFAC SDN & Sanctions List Edge Screener → Address Snapshot & Operator Policy Comparison

### 2026-10-07 (score 77)

First indexed and scored.

## MCP tools (4)

### `verify_id` (~85 tokens)

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

Input parameters:

- `cc` (string)
- `id` (string, required)
- `kind` (string, required)

### `reconcile` (~64 tokens)

reconcile=reconcile_commerce(order:obj!,payments:arr!,delivery:obj?,certify:bool?)->XDR1ExceptionReport

Input parameters:

- `certify` (boolean)
- `delivery` (object)
- `order` (object, required)
- `payments` (array, required)

### `screen_entity` (~56 tokens)

screen_entity=screen_sanctions_exact(entity:str!,jurisdiction:str?,wallet:str?)->XDR1SanctionsVerdict

Input parameters:

- `entity` (string, required)
- `jurisdiction` (string)
- `wallet` (string)

### `solvency_check` (~66 tokens)

solvency_check=balance_check(wallet:str!,asset:enum[USDC|EURC|ETH]?,min_minor:str?)->XDR1SolvencyProof

Input parameters:

- `asset` (string)
- `min_minor` (string)
- `wallet` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/89rat-x402-checks/api#diagnostics

## Score history

- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 81
- 2026-10-14: 80
- 2026-10-13: 80
- 2026-10-12: 79
- 2026-10-10: 78
- 2026-10-07: 77

## Common questions

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

## Links

- Remote endpoint: https://api.code402.dev/mcp
- Repository: https://github.com/89rat/m2m-exchange
- Website: https://hcrb.in/
- Changelog RSS feed: https://verifymcp.io/servers/89rat-x402-checks/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/89rat-x402-checks/api.json
- HTML version of this page: https://verifymcp.io/servers/89rat-x402-checks/api