dev.forestrie/verify
NPM · @FORESTRIE/MCP-VERIFY · SCANNED SEP 21
MCP verification server for Forestrie receipts — offline, no backend, no key, no network
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to forestrie/mcp-verify). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1200 tokens (~60/item across 20 items; 4 tools + 16 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dev.forestrie/verify MCP server?
dev.forestrie/verify runs locally as an npm package, launched with npx -y @forestrie/mcp-verify. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @forestrie/mcp-verify
claude mcp add dev-forestrie-verify -- npx -y @forestrie/mcp-verify
{
"mcpServers": {
"dev-forestrie-verify": {
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-verify"
]
}
}
} {
"servers": {
"dev-forestrie-verify": {
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-verify"
]
}
}
} codex mcp add dev-forestrie-verify -- npx -y @forestrie/mcp-verify
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-forestrie-verify": {
"type": "local",
"command": [
"npx",
"-y",
"@forestrie/mcp-verify"
],
"enabled": true
}
}
} openclaw mcp add dev-forestrie-verify --command npx --arg -y --arg @forestrie/mcp-verify
mcp_servers:
dev-forestrie-verify:
command: "npx"
args: ["-y", "@forestrie/mcp-verify"] {
"McpServers": {
"dev-forestrie-verify": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@forestrie/mcp-verify"
]
}
}
} assistant mcp add dev-forestrie-verify -t stdio -c npx -a -y @forestrie/mcp-verify
{
"mcpServers": {
"dev-forestrie-verify": {
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-verify"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 +1
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.4.0 → 0.4.1 functional
- 13 Sept 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@forestrie/mcp-verify@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | forestrie/mcp-verify |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/forestrie/mcp-verify/.github/workflows/publish.yml@refs/tags/v0.4.1 |
| Rekor log index | 2829231151 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9c3e8d498c9908dbd5ea4b694b610ba5cac878c7396a73c7a1c358a2add6bd81c5a9f8c0255154204936bd9050be7229cfea8edff8bf7ee229bcd2722 |
Background: How many MCP packages publish verified provenance →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
decode_receipt Decode a receipt to JSON ~73
Render a COSE receipt's CBOR as JSON — headers, named labels, payload, signature and inclusion proof. NO VERIFICATION is performed: a receipt that decodes cleanly may still be invalid. Mirrors `forestrie decode-receipt --json`.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | – | yes | the COSE receipt to render |
| Name | Type | Req | Description |
|---|---|---|---|
| byteLength | number | yes | – |
| inclusion | object | yes | – |
| payload | object | yes | – |
| protected | object | yes | – |
| signature | object | yes | – |
| tag | number|null | yes | – |
| unprotected | object | yes | – |
No examples provided.
verify_grant_receipt Verify a grant receipt ~148
Verify a Forestrie grant receipt against the committed grant (Forestrie-Grant COSE Sign1, or raw grant payload CBOR plus an entry id), at a trust root you choose. Mirrors `forestrie verify-grant`. This is the tool that answers the append-authority question: the leaf IS the grant.
| Name | Type | Req | Description |
|---|---|---|---|
| committedGrant | – | yes | Forestrie-Grant COSE Sign1, or raw grant payload CBOR |
| entryId | string | – | required when committedGrant is a raw payload |
| receipt | – | yes | the COSE receipt |
| trust | – | yes | Which anchor you are willing to trust (plan-2609-02 D2/D3) |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | object | – | – |
| diagnostics | array | yes | named notes about what the arithmetic could not separate |
| ok | boolean | yes | – |
| questions | object | yes | the four trust questions. 'not_answered_by_this_root' is a real answer and must be shown to the user, never collapsed into a pass. |
| reason | string | – | – |
| root | string | yes | – |
| stage | string | yes | – |
| stages | array | yes | the mechanical stages, exactly the reference CLI's contract |
| verifier | object | yes | – |
No examples provided.
verify_receipt Verify a payload receipt ~136
Verify a Forestrie receipt against the EXACT registered payload bytes and an entry id, at a trust root you choose. Mirrors `forestrie verify`. Offline: no network, no key, no account. Returns both the mechanical stages and the four trust questions.
| Name | Type | Req | Description |
|---|---|---|---|
| entryId | string | yes | 32 lowercase hex: idtimestamp_be8 || mmrIndex_be8 |
| payload | – | yes | the EXACT registered payload bytes whose SHA-256 is the leaf ContentHash |
| receipt | – | yes | the COSE receipt |
| trust | – | yes | Which anchor you are willing to trust (plan-2609-02 D2/D3) |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | object | – | – |
| diagnostics | array | yes | named notes about what the arithmetic could not separate |
| ok | boolean | yes | – |
| questions | object | yes | the four trust questions. 'not_answered_by_this_root' is a real answer and must be shown to the user, never collapsed into a pass. |
| reason | string | – | – |
| root | string | yes | – |
| stage | string | yes | – |
| stages | array | yes | the mechanical stages, exactly the reference CLI's contract |
| verifier | object | yes | – |
No examples provided.
verify_self Verify this package's own release registration ~158
Verify this package's own release-time self-registration receipt: does the receipt commit the signed statement, does that statement's payload match the bundled provenance.json byte-for-byte, and does its ES256 signature verify under the bundled log owner key? No inputs required. Defaults to the known-log-key root with the bundled key, not genesis — the publications log is a grandchild of the forest root and nothing walks that grant chain yet (docs/self-registration.md). Errors clearly, rather than throwing, when this checkout has no fixtures/self/ bundle (any checkout that is not itself the published tarball).
| Name | Type | Req | Description |
|---|---|---|---|
| root | – | – | Which trust root to run verify_self under. Defaults to known-log-key with the bundled key, not genesis — see docs/self-registration.md. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | object | – | – |
| diagnostics | array | yes | named notes about what the arithmetic could not separate |
| ok | boolean | yes | – |
| questions | object | yes | the four trust questions. 'not_answered_by_this_root' is a real answer and must be shown to the user, never collapsed into a pass. |
| reason | string | – | – |
| root | string | yes | – |
| self | object | yes | – |
| stage | string | yes | – |
| stages | array | yes | the mechanical stages, exactly the reference CLI's contract |
| verifier | object | yes | – |
No examples provided.
What is the dev.forestrie/verify MCP server?
dev.forestrie/verify is an MCP server listed in the public MCP registry as dev.forestrie/verify. MCP verification server for Forestrie receipts, offline, no backend, no key, no network. This page covers its npm package (@forestrie/mcp-verify).
Is the dev.forestrie/verify MCP server safe to use?
dev.forestrie/verify scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.forestrie/verify MCP server expose?
dev.forestrie/verify exposes 4 tools: verify_receipt, verify_grant_receipt, decode_receipt, verify_self. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.
Is the dev.forestrie/verify MCP server still maintained?
dev.forestrie/verify is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the dev.forestrie/verify MCP server under?
dev.forestrie/verify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.