Fetch SCITT receipts and on-chain anchors for offline verification
dev-forestrie-resolve declares 8 capabilities across 8 tools, with 1 critical issue.
Issues
8 of 8 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
8 of 8 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
fetch_scitt_configuration | read |
declared |
query_registration | read |
declared |
fetch_receipt | read |
declared |
fetch_genesis | read |
declared |
fetch_accumulator | read |
declared |
fetch_checkpoint_history | read |
declared |
fetch_ks256_attestation | read |
declared |
verify_fetched_receipt | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-12 | 12 | tools/list answered by the npm package @forestrie/mcp-resolve@0.3.1 (published to npm as @forestrie/mcp-resolve, listed in the official MCP registry as dev.forestrie/resolve 0.3.1), run in an isolated container with no network access and placeholder credentials |
| 2026-10-11 | 12 | tools/list answered by the npm package @forestrie/mcp-resolve@0.2.0 (published to npm as @forestrie/mcp-resolve, listed in the official MCP registry as dev.forestrie/resolve 0.2.0), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.