io.chainhelix/intel
io.chainhelix/intel · 1.0.0
Nine chain onchain intelligence with a verifiable onchain signal attestation stream
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.chainhelix.iostreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 81 tools.
- Protocol
- 2025-06-18
- Calls itself
- chainhelix 1.1.0
- Handshake time
- 321 ms
- HTTP status
- 200
The tools it lists (81, as of 17 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
proof_specThe machine verification spec for the ChainHelix attestation stream
list_revealsMatured signal reveals with Merkle paths. Optional month YYYY-MM and limit
freshnessFree 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
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. Optional date YYYY-MM-DD, default the latest
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 the count. Optional tool name to filter, and limit
verify_revealRecompute the hash and Merkle fold for one reveal by sequence number. Returns each check result plus the data to re-verify independently on chain
attestation_statsLive counts of the attestation stream: committed, anchored, revealed, gaps
attest_specThe machine verification spec for the attestation service, how sealed claims are hashed, put on chain and verified independently
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.chainhelix/intel, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 66 days ago. The registry entry · chainhelix.io