mcp-registry/io.chainhelix/intel · v1.1.0
As of 2026-10-18 23:14 UTC, the Chainhelix Intel MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Nine chain onchain intelligence with a verifiable onchain signal attestation stream
Claude Code
claude mcp add --transport http chainhelix-intel-mcp-server https://mcp.chainhelix.io
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"chainhelix-intel-mcp-server": {
"type": "http",
"url": "https://mcp.chainhelix.io"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
82 of 82 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 →
82 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 →
110 parameter(s) across 59 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 →
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 →
Loading this server's tool list costs an agent ~20,830 tokens before any work — more than 95% 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 →
Handshake + tools/list takes ~2,215 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: 0 tool(s) removed and 564 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 59 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.chainhelix%2Fintel/fixes
{
"name": "attest_status",
"description": "Check one sealed claim by tenant plus seq or hash. Before reveal time only the receipt shows; after it the claim text and salt are included. With a nonce it returns the receipt of a paid answer instead: the sha256 of the answer bytes, its sequence number and, once sealed, the opBNB batch transaction and Merkle path",
"inputSchema": {
"type": "object",
"x-vocab": {
"seq": "agent.seq",
"hash": "onchain.hashApi",
"nonce": "agent.nonce",
"tenant": "agent.tenant"
},
"required": [
"tenant"
],
"x-lexicon": {
"name": "ChainHelix Agentic Lexicon",
"spec": "lexicon_spec",
"resolve": "lexicon_resolve",
"version": "0.2.0",
"bundleSha256": "25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
},
"properties": {
"seq": {
"type": "number"
},
"hash": {
"type": "string"
},
"nonce": {
"type": "string"
},
"tenant": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "attestation_stats",
"description": "Live counts of the attestation stream: committed, anchored, revealed, gaps",
"inputSchema": {
"type": "object",
"x-vocab": {},
"x-lexicon": {
"name": "ChainHelix Agentic Lexicon",
"spec": "lexicon_spec",
"resolve": "lexicon_resolve",
"version": "0.2.0",
"bundleSha256": "25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
},
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "buy_key",
"description": "API keys are not on sale at the moment: every plan answers \"This plan is not on sale.\" and no order is created. When the sale opens this tool returns a payment address, an exact amount in a stablecoin the chosen chain accepts (ethereum, solana and avalanche: USDC or USDT; bnb: USDC, USDT, USD1 or U; polygon: USDC, USDT or USDC.e; tron: USDT; sui: USDC) and a claim token for the chosen plan and payment chain",
"inputSchema": {
"type": "object",
"x-vocab": {
"plan": "payment.plan",
"chain": "onchain.chain",
"email": "identity.email"
},
"required": [
"plan",
"chain"
],
"x-aliases": {
"email": [
"Email",
"EMAIL"
]
},
"x-lexicon": {
"name": "ChainHelix Agentic Lexicon",
"spec": "lexicon_spec",
"resolve": "lexicon_resolve",
"version": "0.2.0",
"bundleSha256": "25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
},
"properties": {
"plan": {
"enum": [
"standard",
"pro",
"alerts"
],
"type": "string"
},
"chain": {
"enum": [
"ethereum",
"solana",
"bnb",
"polygon",
"tron",
"avalanche",
"sui"
],
"type": "string"
},
"email": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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.chainhelix/intel"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.chainhelix/intel"}) over MCP.
hire_plan_healthmon ~938 tokenshire_plan_gridtrader ~823 tokenshire_plan_yieldopt ~715 tokenshire_plan_rebalancer ~678 tokenslexicon_resolve ~363 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%2Fio.chainhelix%2Fintel?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.chainhelix%2Fintel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.chainhelix%2Fintel.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.chainhelix%2Fintel.svg :target: https://glimind.com/server/mcp-registry%2Fio.chainhelix%2Fintel?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:903896a3083b687c…, first seen 2026-10-18, included at leaf 23723 of 23,749. Version history · verify what your client received.
Compare: most reliable data servers · most reliable payments servers · most reliable other servers · most reliable knowledge servers · most reliable security 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-18 23:14 UTC, the Chainhelix Intel MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Chainhelix Intel MCP server advertises 82 tools, including agent_report, agent_standing, attest, attest_spec, attest_status.
Point your MCP client at this streamable-http endpoint: https://mcp.chainhelix.io
Glimind scanned all 82 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.