Policyrecall

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Policy-verified recall and calibration for tool calls via signed operational memory.

VerifiedSTDIODesktop only

Overview

Policyrecall's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Policyrecall in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

policyrecall

policyrecall is a client for a hosted operational-memory service. Once an agent identity is registered, the service can recall a policy-verified compliant version of a tool call you are about to make, and it can calibrate a call against live policy. Requests are signed with a locally held Ed25519 key, so the service can tell that a call really came from the registered agent. One binary serves a command-line interface and a stdio MCP server.

Identity and configuration

Before recall or calibration can work, an identity must exist:

bash
policyrecall achromat_register_identity --user-confirmed true

Registration generates a fresh Ed25519 keypair, computes a small proof-of-work over the public key, and sends the public key to the service. The private key is saved only after the service accepts, as a PKCS#8 PEM file with owner-only permissions (0600). Registering again while a key file already exists is an error — the existing key is never overwritten. Recall and calibrate with no key file fail with an error that says identity setup is required and names the registration step.

Two environment variables configure the client:

VariableDefault
ACHROMAT_BASE_URLhttps://mom.achromat.ai
ACHROMAT_AGENT_KEY_FILE~/.achromat/achromat_agent_key.pem

Unlike the original server, which offers its tools dynamically depending on key state, policyrecall always lists all three tools and applies the state check when a tool is called.

Install

bash
npx @reneturcios/policyrecall --version

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/policyrecall

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

The subcommands mirror the MCP tool names:

bash
policyrecall achromat_register_identity --user-confirmed true
policyrecall achromat_recall \  --domain fintech \  --tool-name send_payment \  --task-description "Pay a verified vendor invoice on time" \  --arguments '{"amount": 42, "currency": "USD"}'
policyrecall achromat_calibrate \  --domain robotics \  --tool-name move_arm \  --task-description "Move the arm to the loading position" \  --arguments '{"joint": 2, "angle": 45}' \  --trap-id trap-7
policyrecall --version

--arguments takes a JSON object. Results print the upstream JSON payload. Exit codes: 0 on success, 1 when a call fails (including a missing identity or an upstream error), 2 for usage errors.

MCP server

The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/policyrecall mcp

MCP client configuration:

json
{  "mcpServers": {    "policyrecall": {      "command": "npx",      "args": ["-y", "@reneturcios/policyrecall", "mcp"],      "env": { "ACHROMAT_BASE_URL": "https://mom.achromat.ai" }    }  }}

Tools

ToolInputWhat it does
achromat_register_identityuser_confirmed (required, must be true)Generate an Ed25519 keypair, solve a small proof-of-work, register the public key, and save the private key locally.
achromat_recalldomain, tool_name, task_description, arguments (all required)Recall a policy-verified compliant version of the described tool call.
achromat_calibratedomain, tool_name, task_description, arguments (required), trap_id (optional)Calibrate the described tool call against live policy.

domain is one of fintech, industrial_iot, robotics, or devsecops. task_description is 16 to 1000 characters, and arguments is the call's argument object, which must not be empty. Recall and calibrate requests are signed with the local key; the service receives the tool name under its tool field.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, fake fetch onlynpm run dev     # run the CLI from source via tsx

Tests use a fake fetch plus real local key generation and signing in temporary directories; no live service call is made.

License

MIT — see LICENSE.

Source: README.md at commit e4ba5d5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts