Canari
Records what a scanner found about an agent component, binds it to the exact artifact bytes it came from, signs it, and lets anyone check the record without trusting us.
Check something right now
| I want to… | Go to |
|---|---|
| Verify a record in my browser, with no install and no network | /verify/ |
| See the raw scan output for 20 PyPI MCP servers, with the re-derivation script | /scan/ |
| Read the append-only ledger and its current head | /log/ |
| See the measurements taken against this ecosystem | /research/ |
Use it
# gate an MCP server before it starts, from an existing client config pip install canari-mcp==0.1.4 canari-mcp-gate --store /path/to/store -- npx -y @modelcontextprotocol/server-filesystem /tmp # verify a record offline, given the published public key canari-verify record.bundle.json --key public_key.json
The gate wraps a stdio MCP entry: it resolves the component in the signed ledger, refuses to start it if the ledger blocks it, and otherwise proxies stdio byte for byte so the protocol is untouched. It is a configuration-level gate — whoever can edit the config can remove it. It is not a policy engine and not tamper-proof.
Why a signature and not a score
A score asks you to trust the scorer. A signature asks you to trust arithmetic. Canari publishes the key, the exact bytes that were hashed, and a verifier that runs offline, so a third party can disagree with our verdict while still confirming the record is the one we signed and has not changed since.
Limits, stated up front
- Records cover the components we have actually scanned — currently 1,311 deep scans plus metadata for ~22,000 registry entries. Anything else returns "no record", which is not a verdict.
- An append-only log proves a record has not changed. It does not prove the record was right.
- Third-party scanners have their own false positives and false negatives; we inherit both. Where a scanner reported nothing, the record says so rather than claiming a pass.
- Every published number carries its population and date. Several earlier figures were corrected in place after review; the corrections are kept in the repository history rather than quietly edited.