Docs

VeriCID guarantees the tool an agent executes is byte-identical to the tool that was registered — dependencies included. It does not claim the tool is safe: that's why every tool runs sandboxed, and why attestations (auditors endorsing immutable CIDs) are a separate layer.

QUICKSTART

Install & lock a tool

Resolution fetches the artifact, hash-verifies it against the registered CID, shows you the sandbox permissions sealed inside that CID, and pins the exact version in vericid.lock. Add --client codex (or claude) to register it with your agent once, without editing MCP JSON.

$ vericid search filecoin --json
$ vericid install @0xb41f7afbc047641ff6fa374c2bf81a4f115c9128/filecoin-network --version 1.0.1 --client codex
  network → api.calibration.node.glif.io, rpc.ankr.com
Approve and pin to vericid.lock? [y/N] y
Codex MCP server "vericid-filecoin-network-…" configured ✓

Run it from your agent

Restart the client and ask it for Filecoin state. The saved MCP entry invokes vericid run with this project's absolute path; every start re-verifies the lock-pinned CID, then launches a long-lived stdio server inside a Deno default-deny sandbox. Future version installs update the pin, not the client config.

$ vericid call @0xb41f7afbc047641ff6fa374c2bf81a4f115c9128/filecoin-network filecoin_chain_head '{}'

# Already installed? Connect it once:
$ vericid connect @0xb41f7afbc047641ff6fa374c2bf81a4f115c9128/filecoin-network --client claude

Publish your own

The packer seals your entrypoint and its entire dependency tree into one self-contained bundle — the CID covers every byte that will execute. Pure-JS in v1; native addons are rejected at publish time.

$ VERICID_AUTHOR_KEY=0x… vericid publish ./my-tool --onchain
packing @you/my-tool@1.0.0 (sealing full dependency closure)...
synapse: uploading bytes to Filecoin warm storage…
onchain: tx 0x…

What a mismatch looks like

Any byte out of place — a rug pull, a swapped description, a compromised mirror — and the local hash check refuses before anything runs. This is the whole product in one error message.

🛑 INTEGRITY FAILURE for @0xb41f…9128/filecoin-network:
  expected bafkreiecu2cn…tamq
  actual   bafkreie7ux4a…jngq
Refusing to run.