io.chainhelix/intel
REMOTE · MCP.CHAINHELIX.IO · SCANNED SEP 26
Nine chain onchain intelligence with a verifiable onchain signal attestation stream
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 81 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11394 tokens (~140/item across 81 items; 81 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 26% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "webhook_unregister" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 82 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.chainhelix/intel MCP server?
io.chainhelix/intel is a hosted endpoint at https://mcp.chainhelix.io/, 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.
remote · mcp.chainhelix.io
claude mcp add --transport http io-chainhelix-intel 'https://mcp.chainhelix.io/'
{
"mcpServers": {
"io-chainhelix-intel": {
"url": "https://mcp.chainhelix.io/"
}
}
} {
"servers": {
"io-chainhelix-intel": {
"type": "http",
"url": "https://mcp.chainhelix.io/"
}
}
} [mcp_servers.io-chainhelix-intel] url = "https://mcp.chainhelix.io/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-chainhelix-intel": {
"type": "remote",
"url": "https://mcp.chainhelix.io/",
"enabled": true
}
}
} openclaw mcp add io-chainhelix-intel --url 'https://mcp.chainhelix.io/' --transport streamable-http
mcp_servers:
io-chainhelix-intel:
url: "https://mcp.chainhelix.io/" {
"McpServers": {
"io-chainhelix-intel": {
"Transport": "http",
"Url": "https://mcp.chainhelix.io/"
}
}
} assistant mcp add io-chainhelix-intel -t streamable-http -u 'https://mcp.chainhelix.io/'
{
"mcpServers": {
"io-chainhelix-intel": {
"type": "http",
"url": "https://mcp.chainhelix.io/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “attest” rewrote its description, which is the text the model reads security
- Tool “cleared_buyer” rewrote its description, which is the text the model reads security
- Tool “lexicon_bundle” rewrote its description, which is the text the model reads security
- Tool “lexicon_spec” rewrote its description, which is the text the model reads security
- Tool “lexicon_statement” rewrote its description, which is the text the model reads security
- Tool “standing_watch” rewrote its description, which is the text the model reads security
- Tool “stream_register” rewrote its description, which is the text the model reads security
- Tool “stream_register_all” rewrote its description, which is the text the model reads security
- Tool “webhook_register” rewrote its description, which is the text the model reads security
- Tool “webhook_status” rewrote its description, which is the text the model reads security
- “webhook_status” added an optional parameter “secret” cosmetic
- 20 Sept 26 0
- New tool “lexicon_bulk” functional
- New tool “lexicon_bundle” functional
- New tool “lexicon_resolve” functional
- New tool “lexicon_spec” functional
- New tool “lexicon_statement” functional
- “freshness” reworded the description of “name” cosmetic
- 19 Sept 26 0
- Tool “screened_payer” rewrote its description, which is the text the model reads security
- New tool “agent_standing” functional
- New tool “standing_bulk” functional
- New tool “standing_spec” functional
- New tool “standing_watch” functional
- 18 Sept 26 0
- Tool “webhook_register” rewrote its description, which is the text the model reads security
- New tool “lead_alerts” functional
- New tool “lead_alert_spec” functional
- New tool “verify_lead_alert” functional
- 17 Sept 26 0
- Tool “cleared_buyer” rewrote its description, which is the text the model reads security
- Tool “screened_payer” rewrote its description, which is the text the model reads security
- Tool “webhook_register” rewrote its description, which is the text the model reads security
- Schema quality: 8474 → 9342 ▼ functional
- New tool “mev_flow_spec” functional
- New tool “mev_pressure” functional
- New tool “stream_register” functional
- New tool “stream_register_all” functional
- New tool “victim_flow” functional
- 15 Sept 26 0
- Tool “freshness” rewrote its description, which is the text the model reads security
- New tool “fill_receipts” functional
- New tool “instrument_signals” functional
- New tool “instrument_spec” functional
- New tool “instrument_state” functional
- New tool “instruments” functional
- New tool “verify_fill” functional
- New tool “verify_instrument_signal” functional
- 9 Sept 26 0
- New tool “buyer_clearance” functional
- New tool “cleared_buyer” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://mcp.chainhelix.io
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.chainhelix.io | CN=YE2,O=Let's Encrypt,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 58dfca8b86ac99ef956724aa8f5dcb222f8 |
| SANs: mcp.chainhelix.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.chainhelix.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| chainhelix.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.chainhelix.io | Verified | 200 | |
| http (plaintext) | http://mcp.chainhelix.io | HTTPS enforced | 301 | https://mcp.chainhelix.io/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lexicon_spec ~100
The ChainHelix Agentic Lexicon: the argument names every tool on this server accepts, with their representation and unit (meanings are in the paid lexicon_resolve, lexicon_bulk and lexicon_bundle); version, bundle hash, namespaces and counts; the entry rule (20 or more independent publishers, or an on-chain or venue standard) and the refusal convention (a call with an unknown name is refused before payment with the accepted names)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleSha256 | string|null | – | – |
| corpus | string | – | – |
| entries | number | yes | – |
| entryRule | string | yes | – |
| howToRead | string | – | – |
| licence | string | – | – |
| name | string | yes | – |
| namespaces | array | – | – |
| refusal | string | yes | – |
| resolve | string | – | – |
| toolsCovered | number | – | – |
| version | string|null | yes | – |
No examples provided.
lexicon_statement ~211
3 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. A signed conformance statement for one agent on the BNB Smart Chain ERC-8004 registry, checked against the current ChainHelix Agentic Lexicon version: every argument schema the agent publishes on its own card and on the MCP endpoints its own registration declares, per tool whether canonical names are accepted, an unknown name is refused before payment, and every argument carries a lexicon id (x-vocab); the unmapped arguments are listed. Signed EIP-191 by the ChainHelix statement signer, bound to the lexicon version, the bundle hash and the card hash. An agent that publishes no argument schemas is refused before any charge
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | the agent's ERC-8004 token id on BNB Smart Chain |
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | number | – | – |
| argumentsMapped | number | – | – |
| argumentsTotal | number | – | – |
| bundleSha256 | string|null | – | – |
| conforms | boolean | – | – |
| error | string | – | – |
| howToVerify | array | – | – |
| lexiconVersion | string|null | – | – |
| message | string | – | – |
| notes | array | – | – |
| receipt | object | – | – |
| result | – | – | – |
| signature | string | – | – |
| signer | string | – | – |
| statement | – | – | – |
| toolsChecked | number | – | – |
| toolsPassing | number | – | – |
No examples provided.
liquidations ~130
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Lending liquidations per chain, protocol and direction over a window: event count, borrowers and liquidators, debt covered and collateral liquidated. window in hours, default 24, max 720. Omit chain for all Chains covered: ethereum, bnb, avalanche, polygon.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
list_attestations ~52
A tenant’s full sealed-claim stream, newest first. Matured claims include their text and salt. Optional limit up to 200
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| tenant | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| records | array | yes | – |
| tenant | string | yes | – |
| total | number | yes | – |
No examples provided.
list_reveals ~40
Matured signal reveals with Merkle paths. Optional month YYYY-MM and limit
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| month | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| latest | array | – | – |
| month | string | – | – |
| months | array | – | – |
| reveals | array | – | – |
No examples provided.
market_state ~131
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Regime, range age, volatility state and momentum per chain: RSI 14 on 1h, 4h and 1d, MACD 12/26/9 on 1h and 4h, the 4h EMA trend and one summary momentum state. Omit chain for all nine
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
mev_bots ~138
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Active MEV bot addresses on a chain: detections, strategy types seen, first and last seen, high confidence flag. Ordered by detections. active_hours default 168, limit default 50, max 200 Chains covered: ethereum, bnb, avalanche, polygon.
| Name | Type | Req | Description |
|---|---|---|---|
| active_hours | number | – | – |
| chain | string | yes | – |
| limit | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| activeHours | number | – | – |
| bots | array | yes | – |
| chain | string | yes | – |
| count | number | – | – |
| latestAt | number|null | – | – |
| meta | object | – | – |
| receipt | object | – | – |
| rules | object | – | – |
| source | string | – | – |
No examples provided.
mev_flow_spec ~80
How the MEV order flow data is made and how to check it yourself: the four chains, the six event types and how they overlap, the detection rules in force and their dates, the per-minute stream event and how to register for it, the fields of every row, and the public RPC calls that re-derive any victim or attacker transaction
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| calibration | string|null | – | – |
| chains | array | – | – |
| fields | object | – | – |
| name | string | – | – |
| overlap | string | – | – |
| rules | object | – | – |
| stats | object | – | – |
| stream | object | – | – |
| toVerify | array | – | – |
| tools | object | – | – |
| types | object | – | – |
No examples provided.
mev_intel ~151
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. MEV event rates per chain and type vs the trailing weekly pace. window in hours, default 24, max 168. Types overlap and must not be summed: a backrun transaction also emits an arbitrage row. NFT coverage is ERC-721 only, so nft_mev excludes all ERC-1155 activity. Chains covered: ethereum, bnb, avalanche, polygon.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
mev_pressure ~234
Requires a ChainHelix API key as bearer token, or 1 cent per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. MEV pressure per pool per minute on one chain: for every pool with detected MEV in the window, rows by type (sandwich, backrun, frontrun, arbitrage, jit, nft_mev), distinct victims and attackers, profit where measured, median gas multiple, first and last event. Plus the per-minute series of the chain, or of one pool when pool is given, and the chain metrics of its newest minute. window in minutes, default 60, max 1440; limit pools, default 50, max 200. Types overlap: a backrun transaction also emits an arbitrage row, so rows is a row count. Chains covered: bnb, ethereum, polygon, avalanche
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| limit | number | – | – |
| pool | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| chainMinute | object|null | – | – |
| error | string | – | – |
| generated | number | – | – |
| latestEventAt | number|null | – | – |
| meta | object | – | – |
| minutes | array | – | – |
| pool | string|null | – | – |
| pools | array | – | – |
| receipt | object | – | – |
| rules | object | – | – |
| source | string | – | – |
| totals | object | – | – |
| windowMinutes | number | – | – |
No examples provided.
open_interest ~124
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Open interest per chain: latest value, the value at the start of the window, change in percent, high and low inside the window and a sampled series. window in hours, default 24, max 720. Omit chain for all nine
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
options_skew ~131
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Bitcoin and Ether options volatility surface from Deribit by horizon (front, short, mid, long): at the money, put and call implied volatility, risk reversal, butterfly, open interest, latest hour against 24 hours earlier within the same moneyness band definition (bandVersion)
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| horizon | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
prices ~87
Requires a ChainHelix API key as bearer token, or 1 cent per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Live price for every chain in one call, the one cent market check. Omit chain for all nine
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
proof_spec ~21
The machine verification spec for the ChainHelix attestation stream
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
receipt_spec ~73
How to verify the receipt on a paid answer yourself: what the receipt hashes, how receipts are batched into one Merkle root, the calldata layout of the seal on opBNB and the steps to check a receipt against it. attest_status with the payment nonce returns the receipt, its batch and its Merkle path
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| batch | string | – | – |
| name | string | – | – |
| receipt | string | – | – |
| seal | object | – | – |
| stats | object | – | – |
| toVerify | array | – | – |
No examples provided.
screened_payer ~191
Requires a ChainHelix API key as bearer token, or 6 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A signed statement on whether a wallet is clear of sanctions lists, the same screen every payer here passes before a settle: the OFAC SDN address list and the on-chain sanctions oracle. Send an EVM address; get the result, both sources, the time of the screen, its expiry after 24 hours, the statement text and its signature from a ChainHelix key that holds no funds. A seller agent checks the signature and the expiry before it negotiates. clear: on neither list; listed: on at least one; partial: one source could not be read
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| network | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string|null | – | – |
| expiresAt | string | – | – |
| howToVerify | array | – | – |
| message | string | – | – |
| meta | object | – | – |
| network | string | – | – |
| payer | string | – | – |
| receipt | object | – | – |
| result | string | – | – |
| screenedAt | string | – | – |
| signature | string | – | – |
| signer | string | – | – |
| sources | object | – | – |
| version | number | – | – |
No examples provided.
search_agents ~129
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Search the ERC-8004 registry on BNB Smart Chain by name and description, joined with ChainHelix live status: alive or hireable with probe age for verified agents, unverified for the rest with the free check link. limit default 20, max 50
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| meta | object | – | – |
| query | string | yes | – |
| receipt | object | – | – |
| registryTotal | number|null | – | – |
| results | array | yes | – |
No examples provided.
session_stats ~88
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Share of price movement per trading session over 7 days. Sessions are Asia London New York in UTC thirds
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
situation_report ~117
Requires a ChainHelix API key as bearer token, or 5 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. The full market picture in one call: market state with momentum (RSI, MACD, 4h trend), price walls, large transfers, bot activity and the Bitcoin queue for every chain in a single report. Omit chain for all nine
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bitcoinQueue | object|null | – | – |
| chains | array | yes | – |
| generated | number | yes | – |
| meta | object | – | – |
| receipt | object | – | – |
No examples provided.
stablecoin_flows ~135
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Stablecoin mints and burns per chain and coin over a window: counts, total dollars, large events, and the net of mints minus burns. window in hours, default 24, max 720. Omit chain for all Chains covered: ethereum, bnb, avalanche, polygon.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
standing_bulk ~255
Requires a ChainHelix API key as bearer token, or 25 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. The standing of up to 25 ERC-8004 agents on BNB Smart Chain in one call, one payment, one signature: for each id the same fields as agent_standing (evidence tier from the paid hires ChainHelix funded and the sealed delivery checks, whether it answers now, the registry feedback rows graded by pattern, the evidence links), and one signed statement over the whole list (EIP-191, the published ChainHelix statement signer, valid 24 hours) with one line per agent: id, tier, reachability, feedback grade. 25 cents for the list against 2 cents per agent one at a time. ChainHelix agents come back as first_party with no verdict and are left out of the statement. Ids are read in the order given; an id that is not a positive integer is refused before payment.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | up to 25 ERC-8004 token ids on BNB Smart Chain |
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | – |
| count | number | yes | – |
| error | string|null | – | – |
| howToVerify | array | – | – |
| meta | object | – | – |
| receipt | object | – | – |
| statement | object|null | – | – |
No examples provided.
standing_spec ~83
What agent_standing measures and how to verify one: the evidence tiers (paid hires ChainHelix funded, sealed delivery checks), the reachability states, the registry feedback grades and why feedback is graded rather than counted, the fixed statement layout, the signer, and the rules (nothing written to the registry, no rating ever sold, ChainHelix agents get no verdict).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | – |
| free | string | – | – |
| howToVerify | array | – | – |
| identityRegistry | string | – | – |
| now | object|null | – | – |
| paid | string | – | – |
| registryFeedbackGrades | object|null | – | – |
| reputationRegistry | string | – | – |
| rules | array | – | – |
| signer | string|null | – | – |
| statementLayout | array | – | – |
| tiers | object|null | – | – |
| version | number | yes | – |
| what | string | yes | – |
No examples provided.
standing_watch ~228
4 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. The standing of one ERC-8004 agent on BNB Smart Chain WATCHED for you: 4 dollars buys 7 days of standing_change messages for one agent id PUSHED to your https url, signed. The baseline standing arrives within five minutes, then one message each time the agent's evidence tier, its reachability (hireable, alive, gated, offline) or its registry feedback grade changes, each carrying the full unsigned standing (the same fields as agent_standing). For the buyer with money in escrow with an agent or an agent listed under its name. Call once per agent id; call again to renew or to watch another; manage with webhook_status and webhook_unregister. Method: standing_spec
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | the ERC-8004 token id on BNB Smart Chain |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| agent | number | – | – |
| daysAdded | number | – | – |
| error | string | – | – |
| events | array | – | – |
| expiresAt | number | – | – |
| id | string | – | – |
| note | string | – | – |
| receipt | object | – | – |
| secret | string | – | – |
| url | string | – | – |
| watches | object | – | – |
No examples provided.
stream_register ~166
4 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. The MEV order flow stream PUSHED to your https URL for one chain: one signed message per completed minute with detected MEV on that chain, each carrying the per-pool rows of that minute (the same rows as mev_pressure). 4 dollars buys 7 days of one chain (bnb, ethereum, polygon or avalanche); call once per chain, and again to renew. Manage with webhook_status and webhook_unregister; the contract is in mev_flow_spec
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| chains | object | – | – |
| daysAdded | number | – | – |
| error | string | – | – |
| events | array | – | – |
| expiresAt | number | – | – |
| id | string | – | – |
| note | string | – | – |
| receipt | object | – | – |
| secret | string | – | – |
| url | string | – | – |
No examples provided.
stream_register_all ~164
10 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. The MEV order flow stream PUSHED to your https URL for all four chains at once (bnb, ethereum, polygon, avalanche): one signed message per chain per completed minute with detected MEV, each carrying the per-pool rows of that minute. 10 dollars buys 7 days of every chain, against 4 dollars per chain one at a time with stream_register. Call again to renew. Manage with webhook_status and webhook_unregister; the contract is in mev_flow_spec
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| chains | object | – | – |
| daysAdded | number | – | – |
| error | string | – | – |
| events | array | – | – |
| expiresAt | number | – | – |
| id | string | – | – |
| note | string | – | – |
| receipt | object | – | – |
| secret | string | – | – |
| url | string | – | – |
No examples provided.
verified_agents ~143
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. ChainHelix Verified, the live map of agents on BNB Smart Chain that are actually running: every ERC-8004 registration is probed from its own on-chain record and only alive and hireable agents are listed, each with its endpoint, skills, probe age in seconds, latency, and the permanent evidence record on BNB Greenfield. Optional status hireable or alive
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| count | number | – | – |
| free_check | string|null | – | – |
| meta | object | – | – |
| method | string|null | – | – |
| probedTotal | number|null | – | – |
| receipt | object | – | – |
| results | array | yes | – |
| version | number|null | – | – |
No examples provided.
verified_delivery ~225
Requires a ChainHelix API key as bearer token, or 5 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A neutral check of one agent hire on BNB Smart Chain, sealed on chain. Send the ERC-8183 job id. The deliverable the provider serves and its permanent copy on BNB Greenfield are fetched and hashed; the hash is compared with the pointer the provider wrote on chain at submission, the permanent copy with the served bytes and with the index; the parties, the time from funding to delivery, the amount paid and the settlement come from the chain. The claim states each check and its result, is hashed and sealed on opBNB from a dedicated key within about two minutes, and stays public. A hire that does not exist or has no deliverable yet is refused before any charge. One claim per hire and deliverable; a repeat check returns the claim on record
| Name | Type | Req | Description |
|---|---|---|---|
| job | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| alreadyOnRecord | boolean | – | – |
| claim | object | – | – |
| committedAt | number | – | – |
| error | string|null | – | – |
| hash | string | – | – |
| lookup | string | – | – |
| meta | object | – | – |
| notChecked | array | – | – |
| note | string | – | – |
| opbnbTx | string|null | – | – |
| receipt | object | – | – |
| seq | number | – | – |
| status | string | – | – |
No examples provided.
verify_fill ~48
Check one fill receipt by fill_id: recompute its hash from its fields and, when sealed, the Merkle root of its batch against the seal transaction
| Name | Type | Req | Description |
|---|---|---|---|
| fill_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| batchRootRecomputes | boolean|null | – | – |
| fill_id | string | – | – |
| found | boolean | – | – |
| hashRecomputes | boolean|null | – | – |
No examples provided.
verify_instrument_signal ~49
Check one instrument signal by seq: its commit status and transaction, and when revealed, whether the hash recomputes from the record and folds into its anchor
| Name | Type | Req | Description |
|---|---|---|---|
| seq | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| anchorRootRecomputes | boolean|null | – | – |
| found | boolean | – | – |
| hashRecomputes | boolean|null | – | – |
| opbnbTx | string|null | – | – |
| revealed | boolean|null | – | – |
| seq | number | – | – |
| status | string|null | – | – |
No examples provided.
verify_lead_alert ~86
Check one lead alert by seq: its commit status and opBNB transaction, and whether it folds into its anchor. Pass the alert you hold (the row from lead_alerts or from a push, with its salt) as alert and the answer says whether its hash recomputes to the sealed one
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | – |
| seq | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| anchorRootRecomputes | boolean|null | – | – |
| found | boolean | – | – |
| hashRecomputes | boolean|null | – | – |
| opbnbTx | string|null | – | – |
| revealed | boolean|null | – | – |
| seq | number | – | – |
| status | string|null | – | – |
No examples provided.
verify_reveal ~46
Recompute the hash and Merkle fold for one reveal by sequence number. Returns each check result plus the data to re-verify independently on chain
| Name | Type | Req | Description |
|---|---|---|---|
| seq | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| anchorBscTx | string|null | – | – |
| found | boolean | yes | – |
| hashRecomputes | boolean | – | – |
| merkleFoldsToAnchorRoot | boolean|null | – | – |
| note | string | – | – |
| opbnbTx | string | – | – |
| status | string | – | – |
| verifyOnChain | string | – | – |
No examples provided.
victim_flow ~211
Requires a ChainHelix API key as bearer token, or 1 cent per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. The order flow that was extracted on one chain, newest first: every detected victim transaction with its hash, the attacker and its transaction, the pool and protocol, block and position, the victim gas price against the chain median, spread, and the profit where measured. Filter by pool and by type (sandwich, backrun, frontrun, jit). window in minutes, default 60, max 1440; limit default 50, max 500. Every hash re-derives from a public RPC. Chains covered: bnb, ethereum, polygon, avalanche
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| limit | number | – | – |
| pool | string | – | – |
| type | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| count | number | – | – |
| error | string | – | – |
| generated | number | – | – |
| latestEventAt | number|null | – | – |
| meta | object | – | – |
| pool | string|null | – | – |
| receipt | object | – | – |
| rules | object | – | – |
| source | string | – | – |
| type | string|null | – | – |
| victims | array | – | – |
| windowMinutes | number | – | – |
No examples provided.
wall_map ~103
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Support and resistance price walls per chain with touch counts, from hourly to weekly market structure, the same wall map the ChainHelix engine trades with. Omit chain for all nine
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
wallet_risk ~124
Requires a ChainHelix API key as bearer token, or 5 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Risk profile of one wallet address across chains: risk score, mixer funding and source, dormancy, transaction count and value, protocols used, bridge count, flagged status, plus its recent bridge, mixer and transfer events. Public onchain behaviour only
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| meta | object | – | – |
| profiled | boolean | yes | – |
| profiles | array | – | – |
| receipt | object | – | – |
| recentEvents | array | – | – |
| source | string|null | – | – |
No examples provided.
webhook_register ~178
70 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. Get ChainHelix events PUSHED to your https URL instead of polling: signal_sealed (the sealed signal stream the moment each signal exists), trade_closed (every finished trade with its result), lead_alert (each lead alert the moment it is written, opt in by name). The MEV flow minute stream is a separate registration, stream_register. 70 cents buys 7 days of delivery; call again with the same URL any time to extend. Deliveries are signed so you can verify each one came from us
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| daysAdded | number | – | – |
| error | string | – | – |
| events | array | – | – |
| expiresAt | number | – | – |
| id | string | – | – |
| note | string | – | – |
| receipt | object | – | – |
| secret | string | – | – |
| url | string | – | – |
No examples provided.
webhook_status ~90
Your registered webhooks for your tenant identity (your paying wallet, or your key id), optionally narrowed to one id. Without secret each webhook shows id, active and expiry only. With the signing secret from registration, that webhook also shows its url, events, chains and watches. Never returns the secret
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| secret | string | – | – |
| tenant | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| found | boolean | yes | – |
| webhooks | array | – | – |
No examples provided.
webhook_unregister ~46
Remove a webhook. Takes the id and the signing secret from registration, only the holder of the secret can remove it
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| secret | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| id | string | – | – |
| removed | boolean | yes | – |
No examples provided.
whale_flows ~107
Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Large transfer counts and USD totals per chain. window in hours default 24 max 168, threshold 500000 USD. Chains covered: every chain except bitcoin
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| window | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | – | – |
| receipt | object | – | – |
| results | array | yes | – |
No examples provided.
What is the io.chainhelix/intel MCP server?
io.chainhelix/intel is an MCP server listed in the public MCP registry as io.chainhelix/intel. Nine chain onchain intelligence with a verifiable onchain signal attestation stream. This page covers its hosted endpoint (https://mcp.chainhelix.io).
Is the io.chainhelix/intel MCP server safe to use?
io.chainhelix/intel scores 74 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.chainhelix/intel MCP server expose?
io.chainhelix/intel exposes 81 tools: proof_spec, list_reveals, freshness, daily_digest, data_changelog, and 76 more. Their descriptions and schemas cost roughly 11,079 tokens of context every time the server is loaded.
Does the io.chainhelix/intel MCP server require authentication?
No. We connected to io.chainhelix/intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.chainhelix/intel MCP server still maintained?
io.chainhelix/intel is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.