
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.
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
- Open Policyrecall in the dashboard and add it to a workspace.
- 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:
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:
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
Or run the container image:
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:
--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:
MCP client configuration:
Tools
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
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
0Version history
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