Verify SCITT receipts from Forestrie transparency logs, offline vs AOTrust Notarization & Evidence Server
Verify SCITT receipts from Forestrie transparency logs, offline is an MCP server published by forestrie.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). AOTrust Notarization & Evidence Server is an MCP server published by aotrust.link. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Verify SCITT receipts from Forestrie transparency logs, offline |  AOTrust Notarization & Evidence Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Downloads/month (npm): 1 183 Downloads/week (npm): 385 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.5.0 Downloads/month (PyPI): 541 Downloads/week (PyPI): 124 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.7.0 Downloads/month (npm): 1 183 Downloads/week (npm): 385 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Verify SCITT receipts from Forestrie transparency logs, offline | AOTrust Notarization & Evidence Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-20 (worse) | 2026-10-24 (better) |
| Where it runs (differs) | On your machine (@forestrie/mcp-verify) | On your machine (aotrust-protocol) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/forestrie/mcp-verify | github.com/gitserge-crypto/aotrust-skills |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Verify SCITT receipts from Forestrie transparency logs, offline
Verify a SCITT receipt under a trust root you hold — offline, no backend, no key, no network
AOTrust Notarization & Evidence Server
Cryptographic proof of existence for AI agents. x402 on Base or Solana, NEAR anchored. Free tier.
How to run each
Verify SCITT receipts from Forestrie transparency logs, offline As a local MCP server: npm package
claude mcp add --transport stdio verify -- npx -y @forestrie/mcp-verifyAOTrust Notarization & Evidence Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Verify SCITT receipts from Forestrie transparency logs, offline publish no settings it asks for, so we do not compare settings.
What it can do: Verify SCITT receipts from Forestrie transparency logs, offline · What it can do: AOTrust Notarization & Evidence Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.