← Index

Sign and register statements on a Forestrie log

dev.forestrie/registerv0.2.0Monitoring & Logs

Sign and register statements on a Forestrie log, verify receipts, buy grants via x402 within caps

The current version, v0.2.0, was published to the official MCP registry on 2026-10-19. It is distributed as @forestrie/mcp-register on npm, filed under Monitoring & Logs by this index, and declares 16 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Sign and register statements on a Forestrie log in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-17 02:01 UTC
screened 2026-10-18tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Tool signs and registers statements on a Forestrie log”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-19).

Contracts can change after screening, with no version bump. The gate pins Sign and register statements on a Forestrie log’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Sign and register statements on a Forestrie log](https://mcpindex.ai/server/dev-forestrie-register) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/dev-forestrie-register">Independent trust record for Sign and register statements on a Forestrie log</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/dev-forestrie-register)](https://mcpindex.ai/server/dev-forestrie-register)
HTML
<a href="https://mcpindex.ai/server/dev-forestrie-register"><img src="https://mcpindex.ai/api/v1/badge/dev-forestrie-register" alt="mcpindex verdict" height="20" /></a>
Environment variables
FORESTRIE_BASE_URL

Canopy SCRAPI base URL used when a call omits baseUrl; also the only origin a payer will pay. No default.

FORESTRIE_ROOT_LOG_ID

The forest's root log id (R in /register/{R}/entries) when a call omits rootLogId.

FORESTRIE_GRANT
secret

Your Forestrie-Grant for the data log, as base64 or a file path, when a call omits grant.

FORESTRIE_AUTHORITY_GRANT
secret

Your authority log's creation grant, for issue_grant, register_grant and delegate_sealing as authority.

FORESTRIE_COORDINATOR_URL

Delegation coordinator URL, for delegate_sealing.

FORESTRIE_KNOWN_SEALER_KEY

The registrar's sealer voucher key, base64 x||y, for delegate_sealing.

MCP_REGISTER_HOME

Directory for key files, grants, registrations and the spend ledger; default ~/.config/forestrie/mcp-register.

MCP_REGISTER_KEY_FILE

The log key file (ES256 JWK, mode 600); created on first use if missing.

MCP_REGISTER_AUTHORITY_KEY_FILE

The authority key file (ES256 JWK, mode 600) that signs child grants; created on first use if missing.

MCP_REGISTER_PAYER_KEY_FILE

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

Most one payment may be, in the asset's atomic units. Required with a payer.

MCP_REGISTER_PAY_MAX_PER_DAY

Most all payments in one UTC day may total, in atomic units. Required with a payer.

MCP_REGISTER_PAY_NETWORK

The one network it pays on; default eip155:84532 (Base Sepolia).

MCP_REGISTER_PAY_ASSET

The one asset it pays in; default USDC on Base Sepolia. Required off the default network.

MCP_REGISTER_PAY_TO

Optional: the only payee address it will pay.

MCP_REGISTER_PAY_ALLOW_MAINNET

Set to 1 to allow paying on a network that is not a testnet; off by default.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Monitoring & Logs