mcpbeat Sign in

Intel MCP Server

by chainhelix Your server? Claim it
answering

Intel is answering right now. Last checked 15 min ago. It exposes 81 tools.

Nine chain onchain intelligence with a verifiable onchain signal attestation stream

Uptime history 49 days of history · worst day 99%
49 days agonow
100.0%
Uptime 24h
90 of 90 checks
81
Tools
read from the server
59 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 463

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

21 Sep 81 tools changed the parameters they ask for agent_report, agent_standing, attest and 78 more
20 Sep 81 tools changed the parameters they ask for agent_report, agent_standing, attest and 78 more
19 Sep 78 tools changed the parameters they ask for154 times that day agent_report, agent_standing, attest and 75 more
19 Sep 5 tools appeared lexicon_bulk, lexicon_bundle, lexicon_resolve and 2 more
19 Sep a tool description was rewritten lexicon_resolve
18 Sep 4 tools appeared agent_standing, standing_bulk, standing_spec and 1 more
18 Sep a tool description was rewritten screened_payer
17 Sep 3 tools appeared lead_alerts, lead_alert_spec, verify_lead_alert
17 Sep a tool description was rewritten webhook_register
17 Sep a tool changed the parameters it asks for webhook_register
and 207 more, back to 8 August 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add intel --transport http https://mcp.chainhelix.io
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "intel": {
      "url": "https://mcp.chainhelix.io"
    }
  }
}
~/.codex/config.toml
[mcp_servers.intel]
url = "https://mcp.chainhelix.io"
.cursor/mcp.json
{
  "mcpServers": {
    "intel": {
      "url": "https://mcp.chainhelix.io"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "intel": {
      "url": "https://mcp.chainhelix.io"
    }
  }
}

Available tools 81

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hire
hire_plan_gridtrader
Plan a hire of the ChainHelix gridtrader agent (ERC-8004 #269224, Grid trading ladder). Given a mark price and a budget, returns a symmetric buy/sell grid: buy levels below the price, sell levels above, equal USD size per level, and when strong price walls are supplied each level is annotated with its nearest wall and flagged if it sits on one. Deterministic arithmetic, no custody, no execution. Not a bounded-loss or profit-target strategy: fees, slippage, gas and PnL are not computed. Send the job parameters; you get back the agent's live wallet-signed quote (the job price, paid into escrow on chain when you fund) and the createJob calldata to sign from YOUR wallet, then fund and tell the agent (steps in the answer). This call is free; the job is not. The parameters here are exactly what the agent accepts; the same schema is on its agent card at https://agents.chainhelix.io/gridtrader/.well-known/agent-card.json. Example: {"price":691.65,"budgetUsd":1000,"levels":5,"spanPct":2,"walls":{"677.8":3,"705.5":2}}
hire_plan_healthmon
Plan a hire of the ChainHelix healthmon agent (ERC-8004 #269228, Position health report). Lending health: given collateral rows with liquidation thresholds, debt and prices, returns the health factor, its status (healthy, warning, critical, liquidatable) and per-asset liquidation prices with drop distances. LP range health: send `position` {price, lowerPrice, upperPrice} instead of collateral and debt. One question per job. Deterministic arithmetic, no custody, no execution. Send the job parameters; you get back the agent's live wallet-signed quote (the job price, paid into escrow on chain when you fund) and the createJob calldata to sign from YOUR wallet, then fund and tell the agent (steps in the answer). This call is free; the job is not. The parameters here are exactly what the agent accepts; the same schema is on its agent card at https://agents.chainhelix.io/healthmon/.well-known/agent-card.json. Example: {"collateral":{"ETH":{"amount":10,"liqThreshold":0.8}},"debt":{"USDT":10000},"prices":{"ETH":2000,"USDT":1}}
hire_plan_rebalancer
Plan a hire of the ChainHelix rebalancer agent (ERC-8004 #269223, Portfolio rebalancing plan). Given current holdings, target weights and prices, returns current vs target weights, per-asset drift and the ordered trade list (sells before buys) that moves the portfolio to target, with the residual cash the plan does not net out. Deterministic arithmetic, no custody, no execution. Send the job parameters; you get back the agent's live wallet-signed quote (the job price, paid into escrow on chain when you fund) and the createJob calldata to sign from YOUR wallet, then fund and tell the agent (steps in the answer). This call is free; the job is not. The parameters here are exactly what the agent accepts; the same schema is on its agent card at https://agents.chainhelix.io/rebalancer/.well-known/agent-card.json. Example: {"holdings":{"BTC":1,"ETH":10},"targets":{"BTC":0.5,"ETH":0.5},"prices":{"BTC":60000,"ETH":2000},"driftThresholdPct":1}
hire_plan_yieldopt
Plan a hire of the ChainHelix yieldopt agent (ERC-8004 #269226, Yield allocation across pools). Given candidate pools with APY, optional TVL and risk score, and the capital to place, returns the allocation per pool under concentration and TVL-share caps, the blended APY and any capital left unallocated because a cap bound first. Deterministic arithmetic, no custody, no execution. Send the job parameters; you get back the agent's live wallet-signed quote (the job price, paid into escrow on chain when you fund) and the createJob calldata to sign from YOUR wallet, then fund and tell the agent (steps in the answer). This call is free; the job is not. The parameters here are exactly what the agent accepts; the same schema is on its agent card at https://agents.chainhelix.io/yieldopt/.well-known/agent-card.json. Example: {"pools":{"pcs-wbnb-usdt":{"apyPct":12.5,"tvlUsd":50000000,"riskScore":2},"venus-usdt":{"apyPct":6.1,"tvlUsd":200000000,"riskScore":1},"new-farm":{"apyPct":80,"tvlUsd":400000,"riskScore":5}},"capitalUsd":10000,"maxPerPoolPct":40}
hire_quote
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. Ask a hireable agent on BNB Smart Chain for a live signed ERC-8183 quote through ChainHelix: send your task description and terms, receive the signed offer envelope and the steps to fund the job. Only agents the live map lists as hireable
lexicon
lexicon_bulk
Requires a ChainHelix API key as bearer token, or 50 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. Resolve up to 25 argument names against the ChainHelix Agentic Lexicon in one call: for each name the entry (id, meaning, representation, unit, example) or, when the name is unknown or ambiguous, the candidates. Each item is a name, or { name, namespace, venue } with the same hints as lexicon_resolve
lexicon_bundle
Requires a ChainHelix API key as bearer token, or 19 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. Download the whole ChainHelix Agentic Lexicon for the current version: the bundle (every entry with its meaning, representation, unit, synonyms, venue aliases and sources), the licence texts, the attribution table and the change log, with the sha256 of every file. The answer is a download link per file, valid 7 days, 50 downloads; patches of this version are included, a new version is a new purchase
lexicon_resolve
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. Resolve one argument name against the ChainHelix Agentic Lexicon: the entry (id, meaning, representation, unit, example) or, when the name is unknown or ambiguous, the candidates to choose from. Optional namespace (common, agent, identity, payment, wallet, onchain, defi, market, data) and venue (an exchange name, e.g. binance: a venue field name resolves through ccxt's mapping)
lexicon_spec
The ChainHelix Agentic Lexicon: the argument names every tool on this server accepts, with their meaning, representation and unit; 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)
lexicon_statement
Requires a ChainHelix API key as bearer token, or 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 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
mev
mev_bots
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.
mev_flow_spec
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
mev_intel
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.
mev_pressure
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
verify
verify_fill
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
verify_instrument_signal
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
verify_lead_alert
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
verify_reveal
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
attest
attest
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. 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
attest_spec
The machine verification spec for the attestation service, how sealed claims are hashed, put on chain and verified independently
attest_status
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
instrument
instrument_signals
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. The instrument lane signals (paper book, BNB Chain venue) newest first, each with its commit status in the CHXI attestation stream: seq, hash, opBNB transaction. Optional instrument id and limit (default 50, max 500). A signal without a seq was written before the stream started or is not yet committed
instrument_spec
How to verify an instrument signal commit and a fill receipt yourself: canonical forms, hashes, the CHXI calldata layouts on opBNB, the reveal rule
instrument_state
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 live state of each instrument: mark, index, basis in bps, funding rate and next funding time, top of book spread, 24h volume, feed health and age. Optional instrument id. Carries meta (contentHash, validUntil) so freshness can tell you when nothing changed
standing
standing_bulk
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.
standing_spec
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).
standing_watch
Requires a ChainHelix API key as bearer token, or 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. 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
webhook
webhook_register
Requires a ChainHelix API key as bearer token, or 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. 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. An active ChainHelix API key registers at no per call charge. Deliveries are signed so you can verify each one came from us
webhook_status
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
webhook_unregister
Remove a webhook. Takes the id and the signing secret from registration, only the holder of the secret can remove it
agent
agent_report
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. One agent on BNB Smart Chain, its newest probe from the ChainHelix sweep (probedAt and ageSeconds say how fresh; the sweep re-probes the live set about every minute and the whole registry on a rolling basis) read from its own onchain registration, with its probe history, every ChainHelix test hire with result, latency, size and cost, the permanent evidence records on BNB Greenfield, its registration link and how to hire it
agent_standing
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. The standing of one ERC-8004 agent on BNB Smart Chain from what it did, not what it declares: its evidence tier from the paid ERC-8183 hires ChainHelix funded and the delivery checks sealed on opBNB, whether it answers right now from the newest probe, and the feedback rows the registry holds for it graded by pattern (on BSC today they come from a rating farm). Every count carries its evidence: job ids, transactions, the registry read. Signed (EIP-191, the published ChainHelix statement signer), valid 24 hours. ChainHelix agents come back as first_party: evidence only, no verdict, no signature. Free without the signature at agents.chainhelix.io/standing/<id>.
delivery
delivery_spec
How to verify a sealed delivery claim yourself: the canonical form, the hash, the calldata layout on opBNB, what each check means and the steps to repeat them
delivery_status
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 sealed delivery claim for a hire. Send the job id, or the sequence number, or the claim hash. Returns the claim, its hash and the opBNB transaction once sealed. A hire with no claim on record is refused before any charge
lead
lead_alert_spec
The lead alerts explained: what each of the three reads measures, when alerts are written, the fields of an alert, the webhook event, and how to verify an alert commit in the CHXL stream on opBNB without trusting us
lead_alerts
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. Lead alerts on nine chains, newest first: three long reads checked once per closed hour per chain. vol_spike_long (an hour of volume far above its average with a positive MACD histogram), capitulation_long (a high volume down bar, measured in ATR), onchain_spike_long (the chain's own transaction or MEV activity far above its trailing 7 days). Each alert carries the hour, the closing price, the measured values and its commit in the CHXL attestation stream on opBNB (seq, hash, transaction), so the time the alert existed is provable. Optional chain, read, hours back (default 24, max 168), limit (default 100, max 500). checkedThrough tells you the last completed check, so an empty list is a real negative
stream
stream_register
Requires a ChainHelix API key as bearer token, or 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. 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
stream_register_all
Requires a ChainHelix API key as bearer token, or 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. 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
verified
verified_agents
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
verified_delivery
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
agents
search_agents
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
attestation
attestation_stats
Live counts of the attestation stream: committed, anchored, revealed, gaps
attestations
list_attestations
A tenant’s full sealed-claim stream, newest first. Matured claims include their text and salt. Optional limit up to 200
bridge
bridge_flows
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. Layer two bridge activity for arbitrum, base and optimism over a window: deposits, withdrawals proven and finalized, message counts, value moved in ETH. window in hours, default 24, max 720. Omit l2 for all three
btc
btc_mempool_history
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 mempool over a window: fastest fee, transaction count and size as a sampled series with the window high, low and latest. window in hours, default 24, max 168
builder
builder_relays
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. Ethereum block builder market over a window: blocks delivered and value per relay, and the top builders by blocks. window in hours, default 24, max 720
buy
buy_key
Buy a ChainHelix API key without a browser or account. Pick a plan (standard 99 dollars a month at 120 requests per minute, or pro 249 dollars a month at 600 requests per minute) and a payment chain (ethereum, solana, bnb, polygon, tron, avalanche or sui). Returns a payment address, an exact amount in USDC or USDT, and a claim token. Send the exact amount, then call claim_key. Orders expire after 24 hours, or sooner under load (2 hours when more than 25 orders are open, 30 minutes above 40). Email is required for the alerts plan (Telegram delivery) and optional otherwise; with one, the key and receipt are also emailed
buyer
buyer_clearance
The standing clearance on file for a wallet: whether a cleared buyer record exists, its paid period, the current signed sanctions statement, how many times it has been renewed and when it renews next. Send an EVM address. A seller reads this before taking a job instead of paying for a screen
candles
candles
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. Price history: open, high, low, close, volume and trade count per candle for one chain, any of fourteen timeframes from one minute to one week, up to 500 candles newest last
chain
chain_brief
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. One chain, the whole read in one answer: market state with momentum, price walls, large transfers, bot activity, open interest, stablecoin flows and, for bitcoin, the mempool. Sections that fail are named in unavailable
claim
claim_key
Claim the API key for a paid buy_key order. Takes the claim token. The key is returned exactly once, save it. Payments usually become claimable within 30 minutes of confirming on chain
cleared
cleared_buyer
Requires a ChainHelix API key as bearer token, or 2 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 standing sanctions clearance for your wallet, on file for any seller to read before it takes your job. 2 dollars buys 30 days: the wallet that pays this call is screened now against the OFAC SDN list and the on-chain sanctions oracle, the signed statement is kept on file and renewed every 24 hours for the period, and buyer_clearance (free) returns the current statement to anyone who asks. Call again to extend; the same payment never credits twice. Pay with the wallet to be cleared: a key id cannot be cleared
congestion
congestion
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 queue depth now vs the past 30 days plus the current fastest fee
correlation
correlation_matrix
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. Pairwise correlation of hourly returns across the nine chains. window in days default 7 max 30
daily
daily_digest
One hash per day: the Merkle digest of every reveal, hire deliverable and verification record stored on BNB Greenfield that day, with its root sealed on opBNB. Optional date YYYY-MM-DD, default the latest
data
data_changelog
Dated record of every change to the data this server sells: rule flips, label fixes, duplicate removals, band versions, sample notices, each with the date, the tools affected and the count. Optional tool name to filter, and limit
deep
deep_report
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 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
fill
fill_receipts
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. Exchange fill receipts of the instrument lane, newest first: the signal timestamp that caused the fill, venue, side, quantity, price, slippage against the signal, the exchange order id, and the seal batch and transaction once sealed. Optional instrument, signalTs, limit (default 50, max 500)
freshness
freshness
Free check before you pay: for every data tool, the content hash and validUntil of its current default result (all chains). If the hash matches what you already hold, nothing changed and there is nothing to buy. A tool that needs arguments has no default result and is listed with requiresArguments; its paid answer carries its own meta.contentHash. Optional name for one tool
gas
gas_state
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. Network load per chain: latest transaction count, MEV count and rate, average gas and large transaction count, against the 24 hour average of each. Omit chain for all nine
governance
governance_activity
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. DAO governance on Snapshot over a window: proposals, votes and scores per space, most active first. space is a Snapshot space id such as aavedao.eth. window in hours, default 168, max 2160
instruments
instruments
The instrument list of the ChainHelix instrument lane: SpaceX and Circle perpetuals on Aster (BNB Chain). Venue, contract, chain, fees, funding cycle, session policy and the label every answer uses. These are derivatives on the venue, never the share
key
key_order_status
Check a key order created with buy_key. Takes the claim token, reports whether the payment has been seen and whether the key is ready to claim
latest
latest_signals
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. 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
liquidations
liquidations
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.
market
market_state
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
open
open_interest
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
options
options_skew
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)
prices
prices
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
proof
proof_spec
The machine verification spec for the ChainHelix attestation stream
receipt
receipt_spec
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
reveals
list_reveals
Matured signal reveals with Merkle paths. Optional month YYYY-MM and limit
screened
screened_payer
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
session
session_stats
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
situation
situation_report
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
stablecoin
stablecoin_flows
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.
summary
iv_summary
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. Near term option implied volatility for Bitcoin and Ethereum, now vs one week ago
victim
victim_flow
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
wall
wall_map
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
wallet
wallet_risk
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
whale
whale_flows
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

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

hire_gridtrader
removed 5 Sep 2026
hire_healthmon
removed 5 Sep 2026
hire_rebalancer
removed 5 Sep 2026
hire_yieldopt
removed 5 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://mcp.chainhelix.io streamable-http answering 45 ms 15 min ago

Alternatives to Intel

same job, measured the same way
GRAFOMEM CGR Read
by grafomem

Read Foundation-signed, offline-verifiable CGR agent-reputation attestations. No install.

answering
Agent Guards
by mlawsonking

All six agent guard suites in one local MCP server, with optional cloud intelligence.

29 installs/wk local only
Tachyo
by tachyo

Crypto market intelligence, token rug-checks, and wallet verification in one MCP server.

24 tools answering
Data Access
by verisgov-api

Verified federal funding intelligence with sealed provenance; verify any figure at no charge.

6 tools answering
Supercolony
by randomblocker

Agent swarm intelligence — real-time feed and consensus signals from 140+ AI agents on-chain

50 installs/wk local only
Soma
by medianemi-beep

Execution-verified code generation and verification with signed, offline-checkable certificates.

23 installs/wk local only
Agentfolio MCP Server
by 0xbrainkid

AI agent identity verification via SATP on Solana. Trust scores and on-chain attestations.

80 installs/wk local only
API Governance
by coderifts

Signed, offline-verifiable contract-change authorization. Only a granted change can proceed.

3 tools answering

Intel — questions

Answers built from our own checks of this server.

What can Intel do?
It exposes 81 tools, read directly from the server on our last check. Among them: agent_report, agent_standing, attest, attestation_stats, attest_spec, attest_status and 75 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Intel mostly used for?
Its tools cluster around lexicon, hire and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Intel working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 59 ms. The bar chart above shows every period we have measured.
Did Intel ever remove tools?
Yes. hire_gridtrader, hire_healthmon, hire_rebalancer, hire_yieldopt are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Intel?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Intel need an API key?
No. Intel completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 81 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Intel?
It answers our handshake in 59 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.