mcp-registry/com.mcpscores/onchain-toolkit · v1.0.2
As of 2026-10-20 05:09 UTC, the Mcpscores Onchain Toolkit MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
The on-chain facts you need in the seconds before you transact.
Claude Code
claude mcp add --transport http mcpscores-onchain-toolkit-mcp-server https://onchain-toolkit.bowling-anthony.workers.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mcpscores-onchain-toolkit-mcp-server": {
"type": "http",
"url": "https://onchain-toolkit.bowling-anthony.workers.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
6 of 6 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 →
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. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.mcpscores%2Fonchain-toolkit/fixes
{
"name": "address_info",
"description": "Native balance, the next nonce to use, and whether the address holds contract code — the three things needed before sending from or to an address. Pass 'token' as well to read an ERC-20 balance for the same address in the same call. Values are read at the latest block, so a reorg can change them. Costs $0.008 USDC per call via x402 on Base.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"chain": {
"type": "string",
"examples": [
"base"
],
"description": "ethereum, base, arbitrum, optimism or polygon. Defaults to base."
},
"token": {
"type": "string",
"examples": [
"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
],
"description": "Optional ERC-20 contract address to also report that token's balance."
},
"address": {
"type": "string",
"examples": [
"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
],
"description": "0x-prefixed 20-byte address."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Balance, next nonce, and whether an address is a contract"
}{
"name": "token_info",
"description": "Read an ERC-20's name, symbol, decimals and total supply straight from the contract on the chain you name, and confirm the address actually has code there. Use before quoting an amount or building a transfer: getting decimals wrong is the classic way to send 1,000,000x the intended value. An address with no code, or a contract that is not an ERC-20, is reported as such and is NOT charged. Costs $0.005 USDC per call via x402 on Base.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"chain": {
"type": "string",
"examples": [
"base"
],
"description": "ethereum, base, arbitrum, optimism or polygon. Defaults to base."
},
"address": {
"type": "string",
"examples": [
"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
],
"description": "0x-prefixed 20-byte contract address."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "ERC-20 token details by contract address"
}{
"name": "tx_status",
"description": "Status of a transaction by hash: success, failed or still pending, with the block it landed in, sender and recipient, value moved, gas used, the fee actually paid, and how many logs it emitted. Use to confirm an action you took really settled rather than assuming it did. An unknown hash is reported as not_found and is NOT charged. Costs $0.005 USDC per call via x402 on Base.",
"inputSchema": {
"type": "object",
"required": [
"hash"
],
"properties": {
"hash": {
"type": "string",
"examples": [
"0x08001b920b214572ff2e7a4fc4560bafa717619b00b91561425ef6a325fdfedb"
],
"description": "0x-prefixed 32-byte transaction hash."
},
"chain": {
"type": "string",
"examples": [
"base"
],
"description": "ethereum, base, arbitrum, optimism or polygon. Defaults to base."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Did this transaction succeed?"
}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/com.mcpscores/onchain-toolkit"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.mcpscores/onchain-toolkit"}) over MCP.
address_info ~253 tokenstoken_info ~234 tokenstx_status ~222 tokensgas_now ~201 tokensrequest_data ~163 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%2Fcom.mcpscores%2Fonchain-toolkit?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Fonchain-toolkit?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Fonchain-toolkit.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Fonchain-toolkit.svg :target: https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Fonchain-toolkit?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:1710a91a2129168d…, first seen 2026-10-17, included at leaf 11216 of 30,914. Version history · verify what your client received.
Compare: most reliable blockchain servers · most reliable other servers · most reliable data 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 05:09 UTC, the Mcpscores Onchain Toolkit MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mcpscores Onchain Toolkit MCP server advertises 6 tools, including address_info, demand_report, gas_now, request_data, token_info.
Point your MCP client at this streamable-http endpoint: https://onchain-toolkit.bowling-anthony.workers.dev/mcp
Glimind scanned all 6 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.