Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Policy-verified recall and calibration for tool calls via signed operational memory.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"policyrecall": {
"command": "npx",
"args": [
"-y",
"@reneturcios/policyrecall",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add policyrecall -- npx -y @reneturcios/policyrecall mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"policyrecall": {
"command": "npx",
"args": [
"-y",
"@reneturcios/policyrecall",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"policyrecall": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/policyrecall",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
Before recall or calibration can work, an identity must exist:
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:
| Variable | Default |
|---|---|
ACHROMAT_BASE_URL | https://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.
npx @reneturcios/policyrecall --version
Or run the container image:
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.
The subcommands mirror the MCP tool names:
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.
The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/policyrecall mcp
MCP client configuration:
{
"mcpServers": { "policyrecall": { "command": "npx", "args": ["-y", "@reneturcios/policyrecall", "mcp"], "env": { "ACHROMAT_BASE_URL": "https://mom.achromat.ai" } } } }
| Tool | Input | What it does |
|---|---|---|
achromat_register_identity | user_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_recall | domain, tool_name, task_description, arguments (all required) | Recall a policy-verified compliant version of the described tool call. |
achromat_calibrate | domain, 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.
npm install
npm run build # tsc -> dist/ npm test # node test runner over test/*.test.ts, fake fetch only npm 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.
MIT — see LICENSE.