io.chainhelix/intel

REMOTE · MCP.CHAINHELIX.IO · SCANNED AUG 9

Nine chain onchain intelligence with a verifiable onchain signal attestation stream

Available components

55 55 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security57

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 23 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
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability49

AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 1873 tokens (~81/item across 23 items; 23 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management17

Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage71

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
0% of tool parameters carry a description.Fail
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.chainhelix.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-chainhelix-intel https://mcp.chainhelix.io/

# ~/.codex/config.toml

[mcp_servers.io-chainhelix-intel]
url = "https://mcp.chainhelix.io/"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-chainhelix-intel": {
      "type": "remote",
      "url": "https://mcp.chainhelix.io/",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-chainhelix-intel --url https://mcp.chainhelix.io/ --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-chainhelix-intel:
    url: "https://mcp.chainhelix.io/"

// mcp.json

{
  "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.

Changelog

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.

9 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1053 → 1873 ▼ functional
- New tool “attest” functional
- New tool “webhook_register” functional
- New tool “prices” functional
- New tool “list_attestations” functional
- New tool “webhook_unregister” functional
- New tool “webhook_status” functional
- New tool “deep_report” functional
- New tool “attest_status” functional
- New tool “attest_spec” functional
8 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
7 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 68 → 75 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “situation_report” functional
- New tool “latest_signals” functional
6 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “session_stats” rewrote its description, which is the text the model reads security
- Tool “whale_flows” rewrote its description, which is the text the model reads security
- Tool “congestion” rewrote its description, which is the text the model reads security
- Tool “correlation_matrix” rewrote its description, which is the text the model reads security
- Tool “iv_summary” rewrote its description, which is the text the model reads security
- Tool “market_state” rewrote its description, which is the text the model reads security
- Tool “mev_intel” rewrote its description, which is the text the model reads security
- Schema quality: 45 → 68 ▼ functional
- Tool “verify_reveal” now declares an output schema ▲ functional
- Tool “whale_flows” now declares an output schema ▲ functional
- Tool “attestation_stats” now declares an output schema ▲ functional
- Tool “congestion” now declares an output schema ▲ functional
- Tool “correlation_matrix” now declares an output schema ▲ functional
- Tool “iv_summary” now declares an output schema ▲ functional
- Tool “list_reveals” now declares an output schema ▲ functional
- Tool “market_state” now declares an output schema ▲ functional
- Tool “mev_intel” now declares an output schema ▲ functional
- Tool “proof_spec” now declares an output schema ▲ functional
- Tool “session_stats” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- New tool “wall_map” functional
5 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
4 Aug 26 52

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 9 Aug 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

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

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/

MCP tools · 23 exposed · ~1,596 tokens

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.

Tool Tokens

attest ~158

Requires a ChainHelix API key as bearer token, or 5 cents in USDC per call paid over x402 on the Base network. Seal any claim on chain now, reveal it later — a track record nobody can backdate. Send your claim as the payload string with an optional revealDelayHours from 1 to 720, default 72. Your identity is your paying wallet, or your key id. ChainHelix seals the exact time of your commitment on the opBNB chain; the claim text and salt publish automatically at reveal time. This attests WHEN you said it, never whether it is true. Verification spec: the free attest_spec tool

Input Output Examples

Name	Type	Req	Description
payload	string	yes	–
revealDelayHours	number	–	–

Name	Type	Req	Description
committedAt	number	–	–
error	string	–	–
hash	string	–	–
note	string	–	–
revealAt	number	–	–
revealDelayHours	number	–	–
seq	number	–	–
status	string	–	–
tenant	string	–	–

No examples provided.

attest_spec ~31

The machine verification spec for the attestation service — how sealed claims are hashed, put on chain and verified independently

Input Output Examples

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

attest_status ~58

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

Input Output Examples

Name	Type	Req	Description
hash	string	–	–
seq	number	–	–
tenant	string	yes	–

Name	Type	Req	Description
found	boolean	yes	–
record	object	–	–

No examples provided.

attestation_stats ~25

Live counts of the attestation stream: committed, anchored, revealed, gaps

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
anchors	number	yes	–
awaitingMaturity	number	yes	–
committed	number	yes	–
gaps	number	yes	–
latestSeq	number	yes	–
revealDelayHours	number	yes	–
revealed	number	yes	–

No examples provided.

congestion ~50

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. Bitcoin queue depth and fee level now vs the past 30 days

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
fastestFee	number	yes	–
median30d	number	yes	–
p90_30d	number	yes	–
pendingTransactions	number	yes	–

No examples provided.

correlation_matrix ~65

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. Pairwise correlation of hourly returns across the nine chains. window in days default 7 max 30

Input Output Examples

Name	Type	Req	Description
window	number	–	–

Name	Type	Req	Description
mean	number\|null	–	–
pairs	array	yes	–
windowDays	number	yes	–

No examples provided.

deep_report ~112

Requires a ChainHelix API key as bearer token, or 25 cents in USDC per call paid over x402 on the Base network. The complete nine chain research brief in one call: the full market report with price walls, large transfers and bot activity, the live signal stream with conviction scores and ranking tiers, cross chain correlations, options volatility, session statistics and the proof stream counters, with links to verify every signal on chain. The most complete single answer this server produces

Input Output Examples

Name	Type	Req	Description
chain	string	–	–

Name	Type	Req	Description
correlations	object\|null	–	–
generated	number	yes	–
optionsVolatility	object\|null	–	–
proof	object\|null	–	–
report	object\|null	–	–
sessions	object\|null	–	–
signals	array\|null	–	–
verify	object	–	–

No examples provided.

iv_summary ~53

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. Near term option implied volatility for Bitcoin and Ethereum, now vs one week ago

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
results	array	yes	–

No examples provided.

latest_signals ~123

Requires a ChainHelix API key as bearer token, or 6 cents in USDC per call paid over x402 on the Base network. The live ChainHelix signal stream, newest first. Each signal names chain, direction, entry price, win probability and a conviction score with its ranking tier, and every one is sealed on chain the moment it exists so the record cannot be edited afterward. Verify any of them with the free proof tools. Optional chain, and limit up to 50

Input Output Examples

Name	Type	Req	Description
chain	string	–	–
limit	number	–	–

Name	Type	Req	Description
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

Input Output Examples

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

Input Output Examples

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 ~62

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. Regime, range age and volatility state per chain. Omit chain for all nine

Input Output Examples

Name	Type	Req	Description
chain	string	–	–

Name	Type	Req	Description
results	array	yes	–

No examples provided.

mev_intel ~78

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. MEV event rates per chain and type vs the trailing weekly pace. window in hours, default 24, max 168

Input Output Examples

Name	Type	Req	Description
chain	string	–	–
window	number	–	–

Name	Type	Req	Description
results	array	yes	–

No examples provided.

prices ~65

Requires a ChainHelix API key as bearer token, or 1 cent in USDC per call paid over x402 on the Base network. Live price for every chain in one call — the one cent market check. Omit chain for all nine

Input Output Examples

Name	Type	Req	Description
chain	string	–	–

Name	Type	Req	Description
results	array	yes	–

No examples provided.

proof_spec ~21

The machine verification spec for the ChainHelix attestation stream

Input Output Examples

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

session_stats ~66

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. Share of price movement per trading session over 7 days. Sessions are Asia London New York in UTC thirds

Input Output Examples

Name	Type	Req	Description
chain	string	–	–

Name	Type	Req	Description
results	array	yes	–

No examples provided.

situation_report ~82

Requires a ChainHelix API key as bearer token, or 5 cents in USDC per call paid over x402 on the Base network. The full market picture in one call: market state, price walls, large transfers, bot activity and the Bitcoin queue for every chain in a single report. Omit chain for all nine

Input Output Examples

Name	Type	Req	Description
chain	string	–	–

Name	Type	Req	Description
bitcoinQueue	object\|null	–	–
chains	array	yes	–
generated	number	yes	–

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

Input Output Examples

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.

wall_map ~81

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 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

Input Output Examples

Name	Type	Req	Description
chain	string	–	–

Name	Type	Req	Description
results	array	yes	–

No examples provided.

webhook_register ~140

Requires a ChainHelix API key as bearer token, or 70 cents in USDC per call paid over x402 on the Base network. Get ChainHelix events PUSHED to your https URL instead of polling: signal_sealed (the sealed signal stream the moment each signal exists) and trade_closed (every finished trade with its result). 70 cents buys 7 days of delivery; call again with the same URL any time to extend. An active ChainHelix API key registers at no per call charge. Deliveries are signed so you can verify each one came from us

Input Output Examples

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	–	–
secret	string	–	–
url	string	–	–

No examples provided.

webhook_status ~65

Your registered webhooks for your tenant identity (your paying wallet, or your key id), optionally narrowed to one id. Requires your tenant so it can only show your own webhooks; never returns the signing secret

Input Output Examples

Name	Type	Req	Description
id	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

Input Output Examples

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 ~77

Requires a ChainHelix API key as bearer token, or 2 cents in USDC per call paid over x402 on the Base network. Large transfer counts and USD totals per chain. window in hours default 24 max 168, threshold 500000 USD

Input Output Examples

Name	Type	Req	Description
chain	string	–	–
window	number	–	–

Name	Type	Req	Description
results	array	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

4 Aug 9 Aug