Skip to content

intel MCP server

io.chainhelix/intelchainhelix.iostreamable-httpv1.0.0Scanned

Nine chain onchain intelligence with a verifiable onchain signal attestation stream

82 tools: 2 can delete or cancel things, 72 change things and 8 only read.

Tools: 2 delete, 0 irreversible, 72 write, 8 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 3
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the intel MCP server can do

The intel MCP server is published by chainhelix.io, a domain the MCP Registry verified. It has 82 tools. It can delete or cancel things (2 tools: webhook_register and webhook_unregister) and create or change data (72 tools: proof_spec, freshness, daily_digest, data_changelog and 68 more). 8 tools only read.

2 tools read private data (list_reveals and webhook_status); 3 tools can send data out of your system (stream_register, stream_register_all and standing_watch).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

82 tools

Deletes or cancels 2Claude Code: deny
  • webhook_registerChainHelix 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 r…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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. Price: 70 cents per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
  • webhook_unregisterRemove a webhook.No findings

    Why it is in this group

    • The description's first verb is "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Remove a webhook. Takes the id and the signing secret from registration, only the holder of the secret can remove it

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
Changes things 72Claude Code: ask
  • agent_reportOne 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 in a continuous pass of about two …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 in a continuous pass of about two to three minutes 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. Price: 5 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • agent_standingThe 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 chec…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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>. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • attestAny claim sealed on chain now and revealed later, a track record nobody can backdate.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Any claim sealed on chain now and revealed 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. Price: 5 cents per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • attest_specThe machine verification spec for the attestation service, how sealed claims are hashed, put on chain and verified independentlyNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The machine verification spec for the attestation service, how sealed claims are hashed, put on chain and verified independently

    Annotations the server declares

    • readOnlyHint: true
  • attestation_statsLive counts of the attestation stream: committed, anchored, revealed, gapsNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Live counts of the attestation stream: committed, anchored, revealed, gaps

    Annotations the server declares

    • readOnlyHint: true
  • bridge_flowsBridge activity over a window.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Bridge activity over a window. Read from the Ethereum side: base and optimism deposits with the ETH they carry, and withdrawals proven and finalized (count only, the events carry no value: valueEth null); arbitrum as L1 to L2 message count only (no value, no withdrawals); polygon_pos, the Polygon PoS bridge predicates: deposit and withdrawal_finalized of ETH and WETH with valueEth, of USDC, USDT and DAI as deposit_usd and withdrawal_finalized_usd with valueUsd, of any other token as deposit_token and withdrawal_finalized_token (count only). Read from the BNB Chain side: opbnb, the opBNB portal, deposits with the BNB they carry (valueBnb) and withdrawals proven and finalized (count only). window in hours, default 24, max 720; each hour is published about 90 minutes after it ends. Omit l2 for all five. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • btc_mempool_historyBitcoin mempool over a window: fastest fee, transaction count and size as a sampled series with the window high, low and latest.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • builder_relaysEthereum block builder market over a window: blocks delivered and value per relay, and the top builders by blocks.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • buy_keyAPI keys are not on sale at the moment: every plan answers "This plan is not on sale." and no order is created.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    API keys are not on sale at the moment: every plan answers "This plan is not on sale." and no order is created. When the sale opens this tool returns a payment address, an exact amount in a stablecoin the chosen chain accepts (ethereum, solana and avalanche: USDC or USDT; bnb: USDC, USDT, USD1 or U; polygon: USDC, USDT or USDC.e; tron: USDT; sui: USDC) and a claim token for the chosen plan and payment chain

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • buyer_clearanceThe 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • candlesPrice 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • chain_briefOne 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 5 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • claim_keyAPI keys are not on sale at the moment and buy_key creates no order, so there is no key to claim.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    API keys are not on sale at the moment and buy_key creates no order, so there is no key to claim. 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

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • cleared_buyerA standing sanctions clearance for your wallet, on file for any seller to read before it takes your job.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. Price: 2 dollars per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • congestionBitcoin queue depth now vs the past 30 days plus the current fastest fee.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Bitcoin queue depth now vs the past 30 days plus the current fastest fee. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • correlation_matrixPairwise correlation of hourly returns across the nine chains.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Pairwise correlation of hourly returns across the nine chains. window in days default 7 max 30. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • daily_digestOne 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • data_changelogDated 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 t…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • deep_reportThe 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 ran…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 25 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • delivery_specHow 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 themNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • fill_receiptsExchange 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 orde…1 finding

    Why it is in this group

    • The name "fill_receipts" says "fill": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "fill_receipts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "fill_receipts" says "fill": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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). Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • freshnessFree check before you pay: for every data tool, the content hash and validUntil of its current default result (all chains).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • gas_stateNetwork load per chain: latest transaction count, MEV count and rate, average gas and large transaction count, against the 24 hour average of each.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • governance_activityDAO governance on Snapshot per space: the proposals ChainHelix tracks for the space (its most recent ones) recorded inside the window, each counted once at its latest recorded stat…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    DAO governance on Snapshot per space: the proposals ChainHelix tracks for the space (its most recent ones) recorded inside the window, each counted once at its latest recorded state, split by state (active, pending, closed), with the latest vote count and score total of those proposals, most voted first. space is a Snapshot space id such as aavedao.eth. window in hours, default 168, max 1440. A proposal is recorded when its state, votes or score change and at least every 6 hours. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • hire_plan_gridtraderPlan a hire of the ChainHelix gridtrader agent (ERC-8004 #269224, Grid trading ladder).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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; an example is in the input schema description.

    Annotations the server declares

    • readOnlyHint: true
  • hire_plan_healthmonPlan a hire of the ChainHelix healthmon agent (ERC-8004 #269228, Position health report).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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; an example is in the input schema description.

    Annotations the server declares

    • readOnlyHint: true
  • hire_plan_rebalancerPlan a hire of the ChainHelix rebalancer agent (ERC-8004 #269223, Portfolio rebalancing plan).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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; an example is in the input schema description.

    Annotations the server declares

    • readOnlyHint: true
  • hire_plan_yieldoptPlan a hire of the ChainHelix yieldopt agent (ERC-8004 #269226, Yield allocation across pools).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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; an example is in the input schema description.

    Annotations the server declares

    • readOnlyHint: true
  • hire_quoteA live signed ERC-8183 quote from a hireable agent on BNB Smart Chain, asked through ChainHelix: send your task description and terms, receive the signed offer envelope and the ste…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    A live signed ERC-8183 quote from a hireable agent on BNB Smart Chain, asked 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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • instrument_signalsThe instrument lane signals (paper book, BNB Chain venue) newest first, each with its commit status in the CHXI attestation stream: seq, hash, opBNB transaction.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • instrument_specHow to verify an instrument signal commit and a fill receipt yourself: canonical forms, hashes, the CHXI calldata layouts on opBNB, the reveal ruleNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How to verify an instrument signal commit and a fill receipt yourself: canonical forms, hashes, the CHXI calldata layouts on opBNB, the reveal rule

    Annotations the server declares

    • readOnlyHint: true
  • instrument_stateThe 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, and reference: the spot token…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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, and reference: the spot token of the same name on BNB Chain (CRCLB, SPCXB) priced from its PancakeSwap v3 USDT pool with the mark against it in bps, and the US equity session of the underlying now (open, weekend, holiday, early close) from the Pyth feed schedule. Optional instrument id. Carries meta (contentHash, validUntil) so freshness can tell you when nothing changed. Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • instrumentsThe instrument list of the ChainHelix instrument lane: SpaceX and Circle perpetuals on Aster (BNB Chain).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • iv_summaryNear term option implied volatility for Bitcoin and Ethereum, now vs one week ago.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Near term option implied volatility for Bitcoin and Ethereum, now vs one week ago. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • latest_signalsThe live ChainHelix signal stream, newest first.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The live ChainHelix signal stream, newest first. Each signal names chain, direction, entry price and a conviction score with its ranking tier, and each one is sealed on the opBNB chain before its outcome exists, typically within 5 minutes of being issued and at most about 30 minutes, so the record cannot be edited afterward. sealedAt is the time the signal was issued, committedAt the time its seal was written on chain. Verify any of them with the free proof tools. Optional chain, and limit up to 50. Price: 6 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • lead_alert_specThe 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • lead_alertsLead alerts on nine chains, newest first: three long reads checked once per closed hour per chain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 6 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • lexicon_bulkUp to 25 argument names resolved against the ChainHelix Agentic Lexicon in one call: for each name the entry (id, meaning, representation, unit, example) or, when the name is unkno…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Up to 25 argument names resolved 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. Price: 50 cents per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: true
  • lexicon_bundleThe whole ChainHelix Agentic Lexicon for the current version as a download: the bundle (every entry with its meaning, representation, unit, synonyms, venue aliases and sources), th…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    The whole ChainHelix Agentic Lexicon for the current version as a download: 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. Price: 19 dollars per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • lexicon_specThe 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
  • lexicon_statementA 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 age…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 3 dollars per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: true
  • liquidationsLending liquidations per chain, protocol and direction over a window: event count, distinct borrowers and liquidators, and per token the amount liquidated (debt covered and collate…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Lending liquidations per chain, protocol and direction over a window: event count, distinct borrowers and liquidators, and per token the amount liquidated (debt covered and collateral seized) with its USD value where the price is certain (USD stablecoins at $1; ETH, BTC, BNB, AVAX and POL and their wrapped tokens at the latest hourly close; other tokens amount only, counted in unpricedLegs). Compound v2 and Venus: the borrowed token from the market that emitted the event; the seized token on events recorded from 2026-10-13. oracle: per group, the liquidations checked for an oracle price update (Chainlink AnswerUpdated or Pyth PriceFeedUpdate) before them in the same transaction (sameTx), in the transaction right before (prevTx) or earlier in the block (sameBlock); null for events before the check started. window in hours, default 24, max 720; each hour is published about 90 minutes after it ends. Omit chain for all Chains covered: ethereum, bnb, avalanche, polygon. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • market_stateRegime, 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • mev_botsActive MEV bot addresses on a chain: detections, strategy types seen, first and last seen, high confidence flag.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • mev_flow_specHow 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-m…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • mev_intelMEV event rates per chain and type vs the trailing weekly pace.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • mev_pool_checkPre-trade MEV check of one pool on one chain: how many of its swaps were sandwiched, backrun, frontrun or JIT-attacked in the window, victims per hour, distinct attackers and the m…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Pre-trade MEV check of one pool on one chain: how many of its swaps were sandwiched, backrun, frontrun or JIT-attacked in the window, victims per hour, distinct attackers and the most active ones, sandwich, backrun, frontrun and JIT rows with a 0 gwei attacker leg, attacker profit where measured with its median, the least the sandwich victims lost, and the newest attack. pool required: a pool contract address, or the 32-byte pool id of a Uniswap v4 or PancakeSwap Infinity pool; window in minutes, default 1440, max 10080. Per pool, not per order: victim trade sizes are not stored. Chains covered: bnb, ethereum, polygon, avalanche. Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • mev_pressureMEV 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • open_interestOpen 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.1 finding

    Why it is in this group

    • The name "open_interest" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "open_interest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "open_interest" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • options_skewBitcoin and Ether options volatility surface from Deribit by expiry horizon: short = expiries 0 to 7 days out, front = 8 to 30 days, mid = 31 to 90 days, long = over 90 days.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Bitcoin and Ether options volatility surface from Deribit by expiry horizon: short = expiries 0 to 7 days out, front = 8 to 30 days, mid = 31 to 90 days, long = over 90 days. At the money, put and call implied volatility, risk reversal, butterfly, open interest, as the newest hourly average against 24 hours earlier within the same moneyness band definition (bandVersion). Each hour is published about 90 minutes after it ends; asOf is the start of the hour. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • pricesLive price for every chain in one call, the one cent market check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Live price for every chain in one call, the one cent market check. Omit chain for all nine. Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • proof_specThe attestor address, the opBNB commit and BNB Smart Chain anchor calldata layouts, the canonical record fields and hash rule, the Merkle rule and the verification and completeness…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The attestor address, the opBNB commit and BNB Smart Chain anchor calldata layouts, the canonical record fields and hash rule, the Merkle rule and the verification and completeness steps: the machine verification spec for the ChainHelix attestation stream

    Annotations the server declares

    • readOnlyHint: true
  • receipt_specHow 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • screened_payerA 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 or…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 6 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • session_statsPer chain, the share of the last 7 days of price movement (sum of hourly high minus low over close) that fell in each session: asia 00:00 to 08:00 UTC, london 08:00 to 16:00 UTC, n…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Per chain, the share of the last 7 days of price movement (sum of hourly high minus low over close) that fell in each session: asia 00:00 to 08:00 UTC, london 08:00 to 16:00 UTC, newyork 16:00 to 24:00 UTC. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • situation_reportThe 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 …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 5 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • stablecoin_flowsStablecoin supply and transfer flow per chain and coin over a window.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Stablecoin supply and transfer flow per chain and coin over a window. Mints and burns of 10,000 USD or more: counts, total dollars, large events, net of mints minus burns. Coins recorded since 2026-09-30T03:30Z: ethereum USDT, USDC, USD1, USDS; bnb USDT, USDC, USD1, U; polygon USDT, USDC, USDC.e; avalanche USDT, USDC; solana USDC, USDT; tron USDT. DAI is recorded as USDS, its new name; USDS on avalanche and solana is answered from recordedSince on its rows. DAI and PYUSD rows end 2026-09-30T03:30Z (recordedUntil on their rows); PYUSD is not recorded. Every recorded coin is answered, with zeros when it had no mint or burn; each row gives recordedSince and windowBeforeRecording, true when the window starts before the coin was recorded. supplyCheck: on EVM chains the token totalSupply is read every minute and compared with the events seen (checks, matched, missed). frozenDestroyed: USDT frozen funds destroyed by Tether (DestroyedBlackFunds) on ethereum and tron, counted from recordedSince (when the count started) by whole UTC day; null before the count started. transfers: on ethereum, bnb, polygon and avalanche, every transfer of more than 0 between two addresses (mints, burns and transfers of 0 left out) of the analysed blocks: count, dollars, five size bands, transfers of 500,000 USD or more with those touching a known exchange address and the five largest, and the blocks seen against the block span (coverage). window in hours, default 24, max 720. Omit chain for all six chains. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • standing_bulkThe 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 hire…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Price: 25 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • standing_specWhat 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
  • standing_watchThe 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.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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. Price: 4 dollars per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • stream_registerThe 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 m…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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. Price: 4 dollars per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • stream_register_allThe 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 …Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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. Price: 10 dollars per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • verified_agentsChainHelix 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 hire…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Many registrations can point at one endpoint: distinctEndpoints counts the endpoints and endpointShared marks the shared ones. Optional status hireable or alive. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • verified_deliveryA neutral check of one agent hire on BNB Smart Chain, sealed on chain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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. Price: 5 cents per call.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
  • verify_fillCheck one fill receipt by fill_id: recompute its hash from its fields and, when sealed, the Merkle root of its batch against the seal transaction1 finding

    Why it is in this group

    • The name "verify_fill" says "fill": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "verify_fill" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "verify_fill" says "fill": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • verify_instrument_signalCheck one instrument signal by seq: its commit status and transaction, and when revealed, whether the hash recomputes from the record and folds into its anchorNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • verify_lead_alertCheck one lead alert by seq: its commit status and opBNB transaction, and whether it folds into its anchor.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • verify_revealRecompute the hash and Merkle fold for one reveal by sequence number.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • victim_flowThe 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 po…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 and attacker gas prices, the attacker gas price over the median gas price of the block, 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. Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • wall_mapSupport and resistance price walls per chain with touch counts and strength, from hourly to weekly market structure, the same wall map the ChainHelix engine trades with: the five s…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Support and resistance price walls per chain with touch counts and strength, from hourly to weekly market structure, the same wall map the ChainHelix engine trades with: the five strongest levels on each side of price, and the nearest of them with its distance in percent. Omit chain for all nine. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • wallet_riskRisk profile of one wallet address across chains: risk score, mixer funding and source, dormancy, transaction count and value, protocols used, bridge count, flagged (true when fund…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Risk profile of one wallet address across chains: risk score, mixer funding and source, dormancy, transaction count and value, protocols used, bridge count, flagged (true when funded by a mixer or on the OFAC SDN list, with flagReasons), plus its recent bridge, mixer and transfer events. sanctioned: on the OFAC SDN address list. entity: the exchange name when the address is a labelled exchange hot wallet or deposit address. A wallet dropped from the live profile table in the last 30 days is answered from its newest saved profile (fromHistory true, evictedAt); history lists the saved profiles of the last 30 days, newest first, up to 20 per chain. Public onchain behaviour only. Price: 5 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • whale_flowsLarge transfer counts and USD totals per chain, one row per transaction over 500,000 USD, with exchangeTouching = transfers from or to a known exchange hot wallet or deposit addres…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Large transfer counts and USD totals per chain, one row per transaction over 500,000 USD, with exchangeTouching = transfers from or to a known exchange hot wallet or deposit address. What is counted: ethereum, bnb, polygon, avalanche native-coin transfers in transfers and totalUsd, and their stablecoin transfers of 500,000 USD or more (USDT, USDC, USD1, USDS, U, USDC.e) in stablecoins, with the blocks read against the block span as coverage; tron TRX and TRC-20 stablecoins; xrp native XRP; sui native SUI; bitcoin since 2026-09-25, the value sent to addresses other than the sender. exchangeTouching is null on bitcoin, tron and sui (too few labelled exchange addresses). Large solana transfers are not captured: the solana row answers null. window in hours default 24 max 168. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
Only reads 8Show 8 read-only tools
  • attest_statusCheck one sealed claim by tenant plus seq or hash.No findings

    Why it is in this group

    • The name "attest_status" says "status": a word for reading.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
  • delivery_statusThe sealed delivery claim for a hire.No findings

    Why it is in this group

    • The name "delivery_status" says "status": a word for reading.
    Description, as the server wrote it
    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. Price: 1 cent per call.

    Annotations the server declares

    • readOnlyHint: true
  • key_order_statusAPI keys are not on sale at the moment and buy_key creates no order, so there is no order to check.No findings

    Why it is in this group

    • The name "key_order_status" says "status": a word for reading.
    Description, as the server wrote it
    API keys are not on sale at the moment and buy_key creates no order, so there is no order to check. 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

    Annotations the server declares

    • readOnlyHint: true
  • lexicon_resolveOne argument name resolved against the ChainHelix Agentic Lexicon: the entry (id, meaning, representation, unit, example) or, when the name is unknown or ambiguous, the candidates …No findings

    Why it is in this group

    • The name "lexicon_resolve" says "resolve": a word for reading.
    Description, as the server wrote it
    One argument name resolved 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). Price: 5 cents per call. A ChainHelix API key does not cover this tool.

    Annotations the server declares

    • readOnlyHint: true
  • list_attestationsA tenant’s full sealed-claim stream, newest first.No findings

    Why it is in this group

    • The name "list_attestations" says "list": a word for reading.
    Description, as the server wrote it
    A tenant’s full sealed-claim stream, newest first. Matured claims include their text and salt. Optional limit up to 200

    Annotations the server declares

    • readOnlyHint: true
  • list_revealsMatured signal reveals, each with its sealed record, salt, hash, opBNB commit transaction, BNB Smart Chain anchor and Merkle path, up to 500 per call; without month, the latest rev…Reads private dataNo findings

    Why it is in this group

    • The name "list_reveals" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "commit": it reads repositories.
    Description, as the server wrote it
    Matured signal reveals, each with its sealed record, salt, hash, opBNB commit transaction, BNB Smart Chain anchor and Merkle path, up to 500 per call; without month, the latest reveals and the list of months. Optional month YYYY-MM and limit

    Annotations the server declares

    • readOnlyHint: true
  • search_agentsAgents in the ERC-8004 registry on BNB Smart Chain matched by name and description, joined with ChainHelix live status: alive or hireable with probe age for verified agents, unveri…No findings

    Why it is in this group

    • The name "search_agents" says "search": a word for reading.
    Description, as the server wrote it
    Agents in the ERC-8004 registry on BNB Smart Chain matched 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. Price: 2 cents per call.

    Annotations the server declares

    • readOnlyHint: true
  • webhook_statusYour registered webhooks for your tenant identity (your paying wallet, or your key id), optionally narrowed to one id.Reads private dataNo findings

    Why it is in this group

    • The name "webhook_status" says "status": a word for reading.

    What it can reach

    • private-dataThe input names a secret (input.secret), and the tool reads: it reads secrets.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:55 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
74
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 74 tools that change things (2 destructive, 72 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.chainhelix.io: tools/list returned 82 tools to an anonymous client, including webhook_register (destructive), webhook_unregister (destructive), proof_spec (write), freshness (write), daily_digest (write) and 69 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "open_interest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "open_interest" says "open": a word for a change.

    What this check looks for
  • The server marks "fill_receipts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "fill_receipts" says "fill": a word for a change.

    What this check looks for
  • The server marks "verify_fill" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "verify_fill" says "fill": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools82 changed.~82 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__intel__list_reveals",
      "mcp__intel__attest_status",
      "mcp__intel__list_attestations",
      "mcp__intel__webhook_status",
      "mcp__intel__key_order_status",
      "mcp__intel__search_agents",
      "mcp__intel__delivery_status",
      "mcp__intel__lexicon_resolve"
    ],
    "ask": [
      "mcp__intel__proof_spec",
      "mcp__intel__freshness",
      "mcp__intel__daily_digest",
      "mcp__intel__data_changelog",
      "mcp__intel__verify_reveal",
      "mcp__intel__attestation_stats",
      "mcp__intel__attest_spec",
      "mcp__intel__attest",
      "mcp__intel__stream_register",
      "mcp__intel__stream_register_all",
      "mcp__intel__standing_watch",
      "mcp__intel__prices",
      "mcp__intel__latest_signals",
      "mcp__intel__situation_report",
      "mcp__intel__deep_report",
      "mcp__intel__verified_agents",
      "mcp__intel__market_state",
      "mcp__intel__mev_intel",
      "mcp__intel__wall_map",
      "mcp__intel__whale_flows",
      "mcp__intel__congestion",
      "mcp__intel__correlation_matrix",
      "mcp__intel__iv_summary",
      "mcp__intel__session_stats",
      "mcp__intel__buy_key",
      "mcp__intel__claim_key",
      "mcp__intel__candles",
      "mcp__intel__open_interest",
      "mcp__intel__stablecoin_flows",
      "mcp__intel__liquidations",
      "mcp__intel__bridge_flows",
      "mcp__intel__mev_bots",
      "mcp__intel__builder_relays",
      "mcp__intel__gas_state",
      "mcp__intel__options_skew",
      "mcp__intel__btc_mempool_history",
      "mcp__intel__governance_activity",
      "mcp__intel__wallet_risk",
      "mcp__intel__chain_brief",
      "mcp__intel__agent_report",
      "mcp__intel__hire_quote",
      "mcp__intel__hire_plan_rebalancer",
      "mcp__intel__hire_plan_gridtrader",
      "mcp__intel__hire_plan_yieldopt",
      "mcp__intel__hire_plan_healthmon",
      "mcp__intel__verified_delivery",
      "mcp__intel__delivery_spec",
      "mcp__intel__screened_payer",
      "mcp__intel__cleared_buyer",
      "mcp__intel__buyer_clearance",
      "mcp__intel__receipt_spec",
      "mcp__intel__instruments",
      "mcp__intel__instrument_state",
      "mcp__intel__instrument_signals",
      "mcp__intel__instrument_spec",
      "mcp__intel__verify_instrument_signal",
      "mcp__intel__fill_receipts",
      "mcp__intel__verify_fill",
      "mcp__intel__mev_pressure",
      "mcp__intel__victim_flow",
      "mcp__intel__mev_pool_check",
      "mcp__intel__mev_flow_spec",
      "mcp__intel__lead_alerts",
      "mcp__intel__lead_alert_spec",
      "mcp__intel__verify_lead_alert",
      "mcp__intel__agent_standing",
      "mcp__intel__standing_bulk",
      "mcp__intel__standing_spec",
      "mcp__intel__lexicon_spec",
      "mcp__intel__lexicon_bulk",
      "mcp__intel__lexicon_statement",
      "mcp__intel__lexicon_bundle"
    ],
    "deny": [
      "mcp__intel__webhook_register",
      "mcp__intel__webhook_unregister"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as intel. Review it before you use it.

Capability tags behind 5 rules
  • mcp__intel__list_reveals private-data
  • mcp__intel__stream_register outbound
  • mcp__intel__stream_register_all outbound
  • mcp__intel__standing_watch outbound
  • mcp__intel__webhook_status private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.chainhelix/intel/verify?hash=8ab550460f517318b5e7e11195b00067ad0f6dd9f2c9b1c4bb9b99a131c86b94" | jq -e '.changed == false'

Pinned hash 8ab550460f51, from Nov 15, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.chainhelix/intel/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.chainhelix/intel
[![Anlyon Radar](https://radar.anlyon.com/badge/io.chainhelix/intel.svg)](https://radar.anlyon.com/servers/io.chainhelix/intel)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

intel MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the intel MCP server safe?

No scan can promise that. What its definitions show: 82 tools, 74 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the intel MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: webhook_register and webhook_unregister.

Can the intel MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the intel MCP server have?

82 tools: 2 destructive, 72 write, 8 read. webhook_register, webhook_unregister, proof_spec, freshness, daily_digest, data_changelog, verify_reveal, attestation_stats and 74 more.

Does the intel MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the intel MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): stream_register, stream_register_all and standing_watch.

Has the intel MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.