Sign and register statements… — Claude Code MCP server
Sign data and record it in a Forestrie log, then check and verify the receipt. The server can also issue child grants and handle their x402 payment within configured caps.
claude mcp add --env FORESTRIE_BASE_URL=<FORESTRIE_BASE_URL> --env FORESTRIE_ROOT_LOG_ID=<FORESTRIE_ROOT_LOG_ID> --env FORESTRIE_GRANT=<FORESTRIE_GRANT> --env FORESTRIE_AUTHORITY_GRANT=<FORESTRIE_AUTHORITY_GRANT> --env FORESTRIE_COORDINATOR_URL=<FORESTRIE_COORDINATOR_URL> --transport stdio sign-and-register-statements-on-a-forestrie-log -- npx -y @forestrie/mcp-registerWhat Sign and register statements on a Forestrie log does
The MCP server signs supplied data with a log key and registers it in a Forestrie transparency log. An agent can check the registration state, wait for sealing, save the receipt, and verify it against the data. The server keeps the signing keys; the model supplies payloads rather than key material or signatures.
A separate workflow issues a child grant and registers it with canopy. Payment can go through x402 within configured caps, or stay with the requester: without a payer configured, the server returns the payment requirements and resumes when the requester supplies payment. Setup requires FORESTRIE_GRANT and FORESTRIE_AUTHORITY_GRANT; registering a grant also uses the authority log’s grant. Payloads can be base64 or a file path, with an explicit content type and a limit of 4 MiB.
What it helps with
- sign data and record it in a Forestrie log
- check registration status and save the receipt
- verify a receipt against its statement
- issue a child grant for a data log
- pay to register a grant within configured caps
Example prompts for the agent
- Sign this file and register it in the Forestrie log.
- Check the registration state, then verify the receipt against the original data.
- Issue a child grant for a data log and register it with payment within the configured caps.
How to install Sign and register statements on a Forestrie log
Platform CLI
claude mcp add --env FORESTRIE_BASE_URL=<FORESTRIE_BASE_URL> --env FORESTRIE_ROOT_LOG_ID=<FORESTRIE_ROOT_LOG_ID> --env FORESTRIE_GRANT=<FORESTRIE_GRANT> --env FORESTRIE_AUTHORITY_GRANT=<FORESTRIE_AUTHORITY_GRANT> --env FORESTRIE_COORDINATOR_URL=<FORESTRIE_COORDINATOR_URL> --transport stdio sign-and-register-statements-on-a-forestrie-log -- npx -y @forestrie/mcp-registerReplace <…> with your own values. 11 more environment variables are in the server README
Platform CLI
codex mcp add sign-and-register-statements-on-a-forestrie-log --env FORESTRIE_BASE_URL=<FORESTRIE_BASE_URL> --env FORESTRIE_ROOT_LOG_ID=<FORESTRIE_ROOT_LOG_ID> --env FORESTRIE_GRANT=<FORESTRIE_GRANT> --env FORESTRIE_AUTHORITY_GRANT=<FORESTRIE_AUTHORITY_GRANT> --env FORESTRIE_COORDINATOR_URL=<FORESTRIE_COORDINATOR_URL> -- npx -y @forestrie/mcp-registerReplace <…> with your own values. 11 more environment variables are in the server README
Config file
{
"mcpServers": {
"sign-and-register-statements-on-a-forestrie-log": {
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-register"
],
"env": {
"FORESTRIE_BASE_URL": "<FORESTRIE_BASE_URL>",
"FORESTRIE_ROOT_LOG_ID": "<FORESTRIE_ROOT_LOG_ID>",
"FORESTRIE_GRANT": "<FORESTRIE_GRANT>",
"FORESTRIE_AUTHORITY_GRANT": "<FORESTRIE_AUTHORITY_GRANT>",
"FORESTRIE_COORDINATOR_URL": "<FORESTRIE_COORDINATOR_URL>"
}
}
}
}Replace <…> with your own values. 11 more environment variables are in the server README
Config file
{
"servers": {
"sign-and-register-statements-on-a-forestrie-log": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-register"
],
"env": {
"FORESTRIE_BASE_URL": "<FORESTRIE_BASE_URL>",
"FORESTRIE_ROOT_LOG_ID": "<FORESTRIE_ROOT_LOG_ID>",
"FORESTRIE_GRANT": "<FORESTRIE_GRANT>",
"FORESTRIE_AUTHORITY_GRANT": "<FORESTRIE_AUTHORITY_GRANT>",
"FORESTRIE_COORDINATOR_URL": "<FORESTRIE_COORDINATOR_URL>"
}
}
}
}Replace <…> with your own values. 11 more environment variables are in the server README
Platform CLI
gemini mcp add -e FORESTRIE_BASE_URL=<FORESTRIE_BASE_URL> -e FORESTRIE_ROOT_LOG_ID=<FORESTRIE_ROOT_LOG_ID> -e FORESTRIE_GRANT=<FORESTRIE_GRANT> -e FORESTRIE_AUTHORITY_GRANT=<FORESTRIE_AUTHORITY_GRANT> -e FORESTRIE_COORDINATOR_URL=<FORESTRIE_COORDINATOR_URL> sign-and-register-statements-on-a-forestrie-log npx -y @forestrie/mcp-registerReplace <…> with your own values. 11 more environment variables are in the server README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Sign and register statements on a Forestrie log
How do I install Sign and register statements on a Forestrie log in Claude Code?
Run `claude mcp add register -e FORESTRIE_GRANT=<FORESTRIE_GRANT> -e FORESTRIE_AUTHORITY_GRANT=<FORESTRIE_AUTHORITY_GRANT> -- npx -y @forestrie/mcp-register`. Replace the grant placeholders with your values.
What does Sign and register statements on a Forestrie log do?
It signs data, records it in a Forestrie log, tracks sealing, and verifies the resulting receipt. It can also issue and register child grants.
How does x402 payment work?
The requester chooses the payment setup: a key file, an embedded payment backend, or manual payment. With no payer configured, the server returns the payment requirements and resumes when the requester supplies payment.
