Verify SCITT receipts from Forestrie transparency logs, offline vs Attester Oracle
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)). Attester Oracle is an MCP server published by maminihds. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  Attester Oracle |
|---|---|---|
| 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: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Attester Oracle |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | On your machine (@forestrie/mcp-verify) | Remote server (attester.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/forestrie/mcp-verify | github.com/maminihds/attester-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
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
Attester Oracle
Verify PyPI and npm packages, symbols, and version diffs against real artifacts. Free, no account.
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-verifyAttester Oracle As a remote MCP server
claude mcp add --transport http attester-mcp https://attester.dev/mcp/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Attester Oracle has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Verify SCITT receipts from Forestrie transparency logs, offline nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Verify SCITT receipts from Forestrie transparency logs, offline · What it can do: Attester Oracle · 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). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.