Is the onchaincheck MCP server down?

mcp-registry/io.github.lx1112/onchaincheck · v1.0.0

Also listed as mcp-registry/io.github.lx1112/agent-data-api · primary listing: mcp-registry/io.github.lx1112/agent-data-api

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 19:08 UTC · handshake 104ms

As of 2026-11-22 19:08 UTC, the onchaincheck MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
803
outages (90d)
0
tools
153

100+ pay-per-call tools: token risk, wallet sanctions screening, onchain data, web, company, AI

Point your MCP client at this streamable-http endpoint: https://onchaincheck.dev/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 5 warning(s) across 153 tool(s); ~37,049 tokens of tool definitions.
Scores higher than 4% of 27,664 MCP servers Glimind has audited.
Its tool list costs an agent ~37,049 tokens per session — more than 99% of servers.
71 → 71 since 2026-11-16
no tool-poisoning patterns
Descriptions90
Safety hints18
Schemas100
Protocol100
Stability88
Token cost35
Reliability100
Client compatibility70

What to fix (7)

153 of 153 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 →

Tools: address_label, address_sanctions_exposure, address_sanctions_screen, agent_access_check, ai_chat and 148 more

153 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 →

4 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 →

Tools: company_hiring_movers, deployer_links, deployer_record, x402_top_sellers

1 parameter(s) across 1 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 →

Tools: chat_completions

Loading this server's tool list costs an agent ~37,049 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. 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 →

In the last 30 days: 0 tool(s) removed and 3 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 →

Auto-fix: 44 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lx1112%2Fonchaincheck/fixes

address_label 1 change
{
  "name": "address_label",
  "description": "What is this address? For 1-10 addresses on Ethereum, Base, Arbitrum, Optimism or Polygon: wallet, contract or EIP-7702 delegated wallet; the verified contract name and proxy implementation (Sourcify); a category such as mixer (Tornado Cash), privacy protocol, DEX router, bridge, Safe multisig, smart wallet, lending, token or stablecoin; ERC-20 details, OFAC SDN status, native balance and flags. Wallets get no owner name. Costs $0.01 USDC on Base via x402.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "chain": {
        "enum": [
          "eth",
          "base",
          "arbitrum",
          "optimism",
          "polygon"
        ],
        "type": "string",
        "description": "Chain (default eth)"
      },
      "address": {
        "type": "string",
        "pattern": "^0x[0-9a-fA-F]{40}$",
        "description": "One address"
      },
      "addresses": {
        "type": "string",
        "pattern": "^[0-9a-fA-Fx,\\s]*$",
        "description": "Or up to 10, comma-separated"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
address_sanctions_exposure 1 change
{
  "name": "address_sanctions_exposure",
  "description": "Has this wallet dealt with sanctioned addresses? Reads up to 4,000 of the wallet's latest transfers (native, internal, ERC-20, NFTs) on Base, Ethereum, Arbitrum, Optimism or Polygon and checks every counterparty against the OFAC SDN list's addresses: each sanctioned counterparty with entity, programs, direction, transfer count, assets and dates. Direct exposure only. Not legal advice. Costs $0.01 USDC on Base via x402.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address"
    ],
    "properties": {
      "chain": {
        "enum": [
          "base",
          "eth",
          "arbitrum",
          "optimism",
          "polygon"
        ],
        "type": "string",
        "description": "Chain to scan (default base)"
      },
      "address": {
        "type": "string",
        "pattern": "^0x[0-9a-fA-F]{40}$",
        "description": "EVM wallet address"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
address_sanctions_screen 1 change
{
  "name": "address_sanctions_screen",
  "description": "Is this address sanctioned? Screens a crypto address against the US Treasury OFAC SDN list's published digital currency addresses (ETH, USDC, USDT, XBT, SOL, TRX and others): the listed entity, programs and listing date on a match, or not found as of the list date. Adds whether it is a wallet (EOA) or contract on Base, Ethereum, Arbitrum, Optimism or Polygon, or a wallet or program-derived address on Solana. Not legal advice. Costs $0.005 USDC on Base via x402.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address"
    ],
    "properties": {
      "chain": {
        "enum": [
          "base",
          "eth",
          "arbitrum",
          "optimism",
          "polygon",
          "solana",
          "other"
        ],
        "type": "string",
        "description": "Chain for the wallet/contract check; defaults to base for 0x addresses, solana for Solana addresses, otherwise other (list check only)"
      },
      "address": {
        "type": "string",
        "pattern": "^[A-Za-z0-9:._-]{14,128}$",
        "description": "Address to screen: 0x (EVM), base58 (Solana), or any other currency's address with chain=other"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

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/io.github.lx1112/onchaincheck"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.lx1112/onchaincheck"}) over MCP.

Passed

Largest tool definitions

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

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.lx1112%2Fonchaincheck.svg)](https://glimind.com/server/mcp-registry%2Fio.github.lx1112%2Fonchaincheck?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lx1112%2Fonchaincheck?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.lx1112%2Fonchaincheck.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:caa0511a57650265…, first seen 2026-11-20, included at leaf 361120 of 384,932. Version history · verify what your client received.

Tools (153)

Compare: most reliable security servers · most reliable ml servers · most reliable productivity servers · most reliable data servers · most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the onchaincheck MCP server down right now?

As of 2026-11-22 19:08 UTC, the onchaincheck MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does onchaincheck MCP server provide?

onchaincheck MCP server advertises 153 tools, including address_label, address_sanctions_exposure, address_sanctions_screen, agent_access_check, ai_chat.

How do I install onchaincheck MCP server?

Point your MCP client at this streamable-http endpoint: https://onchaincheck.dev/mcp

Is the onchaincheck MCP server safe to connect to an AI agent?

Glimind scanned all 153 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.

Operator of onchaincheck MCP server?

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.

Feedback
Help us improve