mcp-registry/online.x-402/mcp · v1.0.0
As of 2026-10-20 01:18 UTC, the X 402 MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.5 hours.
SEC EDGAR company briefs for agents: cited synthesis, XBRL metrics. x402/USDC, no account.
Point your MCP client at this streamable-http endpoint: https://api.x-402.online/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
72 of 72 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
72 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
96 parameter(s) across 65 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,614 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 41 tool(s) removed and 32 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 65 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fonline.x-402%2Fmcp/fixes
{
"name": "chain_address",
"description": "See the USDC an address received and sent on Base, with x402 settlements identified. ERC-20 transfers of an address on Base, incoming and outgoing, with the x402 settlements identified by their EIP-3009 method. Totals, distinct senders, last settlement time. Default token is USDC. Data from the Coinbase CDP on-chain index, last 100 transfers within 60 days, truncation declared. Query: ?address=&token= — $0.005000/call, paid per request via x402 (USDC). Use when asked: \"read the transaction histo",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "domain_health",
"description": "Check whether a domain is reachable and healthy: DNS, certificate, redirects, security headers. One call on a domain: A, AAAA, NS, MX and SPF records; the TLS certificate with issuer, expiry and days left; the HTTP redirect chain hop by hop; and which security headers are present. Read from our infrastructure. Query: ?domain= — $0.005000/call, paid per request via x402 (USDC). Use when asked: \"check whether this domain is healthy\", \"is this domain trustworthy\", \"check dns records and ssl of a do",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "eu_mica-check",
"description": "Is this crypto firm authorised under MiCA in the EU? One call checks the official ESMA register of crypto-asset service providers (CASP) by company name or LEI: authorised or not, home member state, competent authority, authorisation date, the exact services it may provide, and the countries it passports to. Query: ?name=Bitpanda or ?lei=5493007WZ7IFULIL8G21 — $0.010000/call, paid per request via x402 (USDC). Use when asked: \"is this crypto exchange licensed in the eu\", \"mica authorisation check",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/online.x-402/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/online.x-402/mcp"}) over MCP.
chain_allowance ~197 tokenssocial_search ~195 tokensagent_task ~193 tokensfr_analyse-immo_partial ~189 tokensunderstand ~188 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fonline.x-402%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fonline.x-402%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fonline.x-402%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fonline.x-402%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fonline.x-402%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f918adc5835895bc…, first seen 2026-10-19, included at leaf 26905 of 33,983. Version history · verify what your client received.
Compare: most reliable other servers · most reliable search servers · most reliable ml servers · most reliable knowledge servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 01:18 UTC, the X 402 MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 25.5 hours.
X 402 MCP server advertises 72 tools, including agent_task, amazon, apify_preflight, brief, callbacks.
Point your MCP client at this streamable-http endpoint: https://api.x-402.online/mcp
Glimind scanned all 72 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.