# dev.forestrie/verify (npm · @forestrie/mcp-verify)

MCP verification server for Forestrie receipts — offline, no backend, no key, no network

- Trust score: 86/100 (high trust)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@forestrie/mcp-verify`: 86/100 (this document), [markdown](https://verifymcp.io/servers/dev-forestrie-verify/forestrie-mcp-verify.md), [page](https://verifymcp.io/servers/dev-forestrie-verify/forestrie-mcp-verify)

## Channel facts

- Registry: `npm`
- Package: `@forestrie/mcp-verify`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 101 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to forestrie/mcp-verify).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1200 tokens (~60/item across 20 items; 4 tools + 16 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add dev-forestrie-verify -- npx -y @forestrie/mcp-verify
```

### Cursor

```json
{
  "mcpServers": {
    "dev-forestrie-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@forestrie/mcp-verify"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-forestrie-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@forestrie/mcp-verify"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-forestrie-verify -- npx -y @forestrie/mcp-verify
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-forestrie-verify": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@forestrie/mcp-verify"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-forestrie-verify --command npx --arg -y --arg @forestrie/mcp-verify
```

### Hermes

```yaml
mcp_servers:
  dev-forestrie-verify:
    command: "npx"
    args: ["-y", "@forestrie/mcp-verify"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-forestrie-verify": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@forestrie/mcp-verify"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-forestrie-verify -t stdio -c npx -a -y @forestrie/mcp-verify
```

### Other

```json
{
  "mcpServers": {
    "dev-forestrie-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@forestrie/mcp-verify"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 86, +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.

### 2026-09-18 (score 85, +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.

### 2026-09-16 (score 84, +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.

### 2026-09-15 (score 83, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 68, +1)

- [security regression] Tool safety: pass → unverified
- [security improvement] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.4.0 → 0.4.1

### 2026-09-13 (score 67)

First indexed and scored.

## MCP tools (4)

### `verify_receipt` (~136 tokens)

Verify a payload receipt

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.

Input parameters:

- `entryId` (string, required): 32 lowercase hex: idtimestamp_be8 || mmrIndex_be8
- `payload` (required): the EXACT registered payload bytes whose SHA-256 is the leaf ContentHash
- `receipt` (required): the COSE receipt
- `trust` (required): Which anchor you are willing to trust (plan-2609-02 D2/D3)

Output parameters:

- `anchor` (object)
- `diagnostics` (array): named notes about what the arithmetic could not separate
- `ok` (boolean)
- `questions` (object): 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)
- `stage` (string)
- `stages` (array): the mechanical stages, exactly the reference CLI's contract
- `verifier` (object)

### `verify_grant_receipt` (~148 tokens)

Verify a grant receipt

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.

Input parameters:

- `committedGrant` (required): Forestrie-Grant COSE Sign1, or raw grant payload CBOR
- `entryId` (string): required when committedGrant is a raw payload
- `receipt` (required): the COSE receipt
- `trust` (required): Which anchor you are willing to trust (plan-2609-02 D2/D3)

Output parameters:

- `anchor` (object)
- `diagnostics` (array): named notes about what the arithmetic could not separate
- `ok` (boolean)
- `questions` (object): 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)
- `stage` (string)
- `stages` (array): the mechanical stages, exactly the reference CLI's contract
- `verifier` (object)

### `decode_receipt` (~73 tokens)

Decode a receipt to JSON

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`.

Input parameters:

- `receipt` (required): the COSE receipt to render

Output parameters:

- `byteLength` (number)
- `inclusion` (object)
- `payload` (object)
- `protected` (object)
- `signature` (object)
- `tag` (number|null)
- `unprotected` (object)

### `verify_self` (~158 tokens)

Verify this package's own release registration

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).

Input parameters:

- `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.

Output parameters:

- `anchor` (object)
- `diagnostics` (array): named notes about what the arithmetic could not separate
- `ok` (boolean)
- `questions` (object): 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)
- `self` (object)
- `stage` (string)
- `stages` (array): the mechanical stages, exactly the reference CLI's contract
- `verifier` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-forestrie-verify/forestrie-mcp-verify#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 85
- 2026-09-18: 85
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 68
- 2026-09-13: 67

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@forestrie/mcp-verify
- Socket report: https://socket.dev/npm/package/@forestrie/mcp-verify
- Repository: https://github.com/forestrie/mcp-verify
- Changelog RSS feed: https://verifymcp.io/servers/dev-forestrie-verify/forestrie-mcp-verify.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-forestrie-verify/forestrie-mcp-verify.json
- HTML version of this page: https://verifymcp.io/servers/dev-forestrie-verify/forestrie-mcp-verify