Fetch SCITT receipts and on-chain anchors for offline verification
Fetch a SCITT receipt, its genesis and on-chain accumulator for @forestrie/mcp-verify to verify
Connector by forestrie.dev · Domain verified by the MCP Registry
Chalk Labs
Need help deploying Fetch SCITT receipts and on-chain anchors for offline verification?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/forestrie-dev-resolve
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 8 read · 0 write · 0 deleteRead-only
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Node.js package
Tools by what they do 8
Read from the source code; the running server may list different tools.
Read 8 · Look things up without changing anything.
fetch_accumulatorfetch_checkpoint_historyfetch_genesisfetch_ks256_attestationfetch_receiptfetch_scitt_configurationquery_registrationverify_fetched_receipt
Secrets and settings it asks for
Other settings (environment variables or headers).
FORESTRIE_BASE_URLFORESTRIE_RPC_URL
Network hosts it talks to 6
api-a.forest-2.forestrie.dev· found in codeapi-b.forest-2.forestrie.dev· found in codeapi.nuget.org· found in codedocker.io· found in codegithub.com· found in codegitlab.com· found in code
Tools (8)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
fetch_accumulatorFetch accumulator from chainread-onlyRead the log's published accumulator from the univocity contract at your rpcUrl: eth_chainId, then eth_getBlockByNumber latest, then one eth_call logState(logId) at that block. The contract address and chain id come from a genesis you hold ({genesis, rpcUrl, logId}) or are given explicitly ({rpcUrl, univocity, logId, chainId?}); a chain id mismatch is reported as a problem before any call. Optionally pass forReceipt (the receipt bytes with the registered payload and its entryId, or the committed grant bytes with grant true; bytes base64): if later growth has buried that receipt's peak, so the …
fetch_checkpoint_historyFetch checkpoint history from chainread-onlyRead the log's published checkpoints from the univocity contract's CheckpointPublished events at your rpcUrl, newest first, in windows of history.chunkBlocks (default 10000) walking back from the latest block to history.fromBlock, or for at most history.maxBlocks (default 200000): one eth_getLogs per window, never an unbounded scan. The contract address and chain id come from a genesis you hold or are given explicitly, as for fetch_accumulator. Returns each checkpoint's size, accumulator, block number, block hash and transaction hash, plus the same checkpoint as a known-accumulator snapshot (b…
fetch_genesisFetch genesis documentread-onlyGET {baseUrl}/api/forest/{logId}/genesis: the forest's genesis document as CBOR, base64-encoded, with what it carries decoded: the chain binding (univocity contract address, chain id, forest log id) and, for an ES256 forest, the bootstrap public key as bootstrapKeyXy (x‖y hex). Both are read from these bytes, so they stand exactly where the copy stands. For capture: obtain it once, keep it, and pass it as bytes from then on. A copy obtained at check time is not the genesis trust root as intended, and its chain binding and bootstrap key are likewise the operator's claim today; keep the copy fro…
fetch_ks256_attestationFetch KS256 attestation from chainread-onlyFor a receipt whose delegation certificate is signed by a contract KS256 root (a Safe, say): ask the contract whether it accepts that certificate, and return the answer as an attestation @forestrie/mcp-verify can consume offline. Reads the chain at your rpcUrl (this tool does; mcp-verify never does): eth_chainId, eth_getBlockByNumber for your block (default latest), then eth_getCode at the root and one eth_call isValidSignature(digest, signature), where digest and signature come from the receipt's certificate. Both state reads are pinned by the block's hash (EIP-1898, requireCanonical), so the…
fetch_receiptFetch receiptread-onlyGET a receipt: either by receiptUrl (as returned by query_registration) or by {baseUrl, bootstrapLogId, logId, massifHeight, entryId}. Returns the receipt bytes base64-encoded, the verifier's decoding of them, and receiptLogId: the log the receipt's delegation certificate names, which is the operator's statement like the rest of the receipt. A 404 is the structured problem not_found carrying the operator's own title (for example 'Entry receipt not found (checkpoint missing)' for a wrong massif height); it is never reported as pending, because a receipt URL the operator holds nothing at does no…
fetch_scitt_configurationFetch SCITT configurationread-onlyGET {baseUrl}/.well-known/scitt-configuration: the transparency service's self-description (service id, base URL, supported algorithms), returned as JSON. Provenance: fetched. Supports: none of the four questions; this is what the operator says about itself.
query_registrationQuery registration statusread-onlyOne GET of {baseUrl}/logs/{bootstrapLogId}/{logId}/entries/{contentHash}, where contentHash is the hex sha256 of the signed statement bytes. Returns pending (with retryAfterMs when the server said so) or the receipt's URL, which includes the massif height, and the entry id. pending is the operator's answer for any content hash its sequencing index does not hold yet, including one that was never registered: the operator does not distinguish the two, so a retry only helps for a statement you know was submitted. receipt-available is the index's answer, not proof the receipt is written: fetch_rece…
verify_fetched_receiptFetch and verify receiptread-onlyFetch a receipt (as fetch_receipt) and verify it with @forestrie/mcp-verify's core under a trust root you supply as bytes (genesis, keyXy, accumulator, or checkpoints; each {b64} or {path}) or under an accumulator read from the chain in this call ({root: 'known-accumulator', chain: {genesis, rpcUrl, logId?} or {rpcUrl, univocity, logId?, chainId?}}). A genesis fetched in the same call is never the root. The result is the verifier's own: stages, the four questions (sealing, split-view, append-authority, attribution; not_answered_by_this_root is a real answer) and diagnostics, passed through una…
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 328
- Last commit
- Oct 20, 2026 (10 days ago)
- Last release
- Oct 20, 2026 (10 days ago)
- Last package publish
- Oct 20, 2026 (10 days ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
dev.forestrie/resolve- Version
- 0.4.1
- Auth
- No auth
- Packages
- npm @forestrie/mcp-resolve
- License
- MIT
- Repository
- github.com/forestrie/mcp-resolve
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from forestrie.dev
- 0.624score
Verify SCITT receipts from Forestrie transparency logs, offline
forestrie.dev
Verify a SCITT receipt under a trust root you hold — offline, no backend, no key, no network
ConnectorAFreshness: ALocalRead-only↓ 385/wkClaude Code +5 - 0.621score
Sign and register statements on a Forestrie log
forestrie.dev
Sign and register statements on a Forestrie log, verify receipts, buy grants via x402 within caps
ConnectorAFreshness: ALocal↓ 268/wkClaude Code +5
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get Fetch SCITT receipts and on-chain anchors for offline verification running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
Fetch SCITT receipts and on-chain anchors for offline verification MCP server. Agent Mart. https://agentmart.dev/connectors/forestrie-dev-resolve (last updated 2026-10-24)