Sign and register statements on a Forestrie log

dev.forestrie/register

7/7 checks passed
Runs locally
2 secrets
★ 0 GitHub stars
Updated 2026-10-20
Health score 51

About Sign and register statements on a Forestrie log

Sign and register statements on a Forestrie log is an MCP server published by forestrie.dev. Sign and register statements on a Forestrie log, verify receipts, buy grants via x402 within caps

It runs on your own machine: your AI client starts it from the npm package @forestrie/mcp-register at version 0.2.1.

It asks for 2 secrets: FORESTRIE_GRANT and FORESTRIE_AUTHORITY_GRANT. Give it a key with the least access that still works.

Version 0.2.1 was published on 20 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

Variable	Required	Secret	Description
`FORESTRIE_BASE_URL`	No	No	Canopy SCRAPI base URL used when a call omits baseUrl; also the only origin a payer will pay. No default.
`FORESTRIE_ROOT_LOG_ID`	No	No	The forest's root log id (R in /register/{R}/entries) when a call omits rootLogId.
`FORESTRIE_GRANT`	No	Yes	Your Forestrie-Grant for the data log, as base64 or a file path, when a call omits grant.
`FORESTRIE_AUTHORITY_GRANT`	No	Yes	Your authority log's creation grant, for issue_grant, register_grant and delegate_sealing as authority.
`FORESTRIE_COORDINATOR_URL`	No	No	Delegation coordinator URL, for delegate_sealing.
`FORESTRIE_KNOWN_SEALER_KEY`	No	No	The registrar's sealer voucher key, base64 x\|\|y, for delegate_sealing.
`MCP_REGISTER_HOME`	No	No	Directory for key files, grants, registrations and the spend ledger; default ~/.config/forestrie/mcp-register.
`MCP_REGISTER_KEY_FILE`	No	No	The log key file (ES256 JWK, mode 600); created on first use if missing.
`MCP_REGISTER_AUTHORITY_KEY_FILE`	No	No	The authority key file (ES256 JWK, mode 600) that signs child grants; created on first use if missing.
`MCP_REGISTER_PAYER_KEY_FILE`	No	No	Optional payer: a file holding your EVM key (0x + 64 hex, mode 600). Unset means relay mode: nothing is spent, your own x402 wallet pays.
`MCP_REGISTER_PAY_MAX_PER_CALL`	No	No	Most one payment may be, in the asset's atomic units. Required with a payer.
`MCP_REGISTER_PAY_MAX_PER_DAY`	No	No	Most all payments in one UTC day may total, in atomic units. Required with a payer.
`MCP_REGISTER_PAY_NETWORK`	No	No	The one network it pays on; default eip155:84532 (Base Sepolia).
`MCP_REGISTER_PAY_ASSET`	No	No	The one asset it pays in; default USDC on Base Sepolia. Required off the default network.
`MCP_REGISTER_PAY_TO`	No	No	Optional: the only payee address it will pay.
`MCP_REGISTER_PAY_ALLOW_MAINNET`	No	No	Set to 1 to allow paying on a network that is not a testnet; off by default.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/forestrie/mcp-register
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for 2 secrets: FORESTRIE_GRANT, FORESTRIE_AUTHORITY_GRANT
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via domain forestrie.dev
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	@forestrie/mcp-register@0.2.1 runs nothing at install
Code red flags	Pass	Read 84 files in @forestrie/mcp-register@0.2.1: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 84 files, including comments and the README

Popularity & health: 51 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity9 / 40

0 GitHub stars, 228 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-20, no GitHub release, 0 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 8 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`dev.forestrie/register`
Publisher	Domain forestrie.dev
How the name is verified	Name verified via domain forestrie.dev. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	npm `@forestrie/mcp-register` 0.2.1 (stdio)
Version	0.2.1
Published	2026-10-20
Last updated	2026-10-20
Source repository	https://github.com/forestrie/mcp-register
Website	https://github.com/forestrie/mcp-register#readme
Category	Analytics & monitoring (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "register": {
      "command": "npx",
      "args": [
        "-y",
        "@forestrie/mcp-register@0.2.1"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/dev-forestrie-register.json. Text inside it that came from the publisher is data, not instructions.