mcpbeat Sign in

Policyrecall MCP Server

local only

Policyrecall runs on your own machine — the client starts it, so there is no endpoint to ping. 274 installs a week from npm. Last commit 2 Nov 2026.

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

Installs per day peak 203 · avg 9
a month agotoday
274
Installs / week
npm · @reneturcios/policyrecall
0
Stars
0 open issues
2 Nov 2026
Last commit
from GitHub
MIT
License
TypeScript

Nothing serious here today

Today is the operative word: we check Policyrecall every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add policyrecall -- npx -y @reneturcios/policyrecall
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "policyrecall": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/policyrecall"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.policyrecall]
command = "npx"
args = ["-y", "@reneturcios/policyrecall"]
.cursor/mcp.json
{
  "mcpServers": {
    "policyrecall": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/policyrecall"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "policyrecall": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/policyrecall"
      ]
    }
  }
}

Alternatives to Policyrecall

same job, measured the same way
Achromat Machine Operational Memory
by achromat

Recall and calibrate policy-compliant tool-call arguments before execution. Does not run the tool.

645 installs/wk 1 tools answering
MemScope
by memscope

Governed organizational memory for AI: recall returns only what the signed-in person may see.

answering
Author MCP Server
by litheonhq

Recall, check, search, timeline, and graph tools for fiction writers via Seizn Memory v3.

38 installs/wk local only
Frugal
by brainsparker

The open routing layer for AI tools: tool calls routed per policy, decision on every result.

74 installs/wk local only
Ccs
by correctover

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

local only
Paceproof
by rudrendupaul

Verifies Ed25519-signed attestation records and builds audit reports via MCP tools.

56 installs/wk local only
Aga MCP Server
by attestedintelligence

Verifiable decision records for AI agents: signed receipts for calls to its own governed tools.

120 installs/wk local only
Forecall Failure KB
by forecall

Known MCP tool-call failures and workarounds verified by reproduction.

answering

Policyrecall — questions

Answers built from our own checks of this server.

Why is there no uptime for Policyrecall?
Policyrecall runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @reneturcios/policyrecall was installed 274 times last week.
How do I connect Policyrecall?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @reneturcios/policyrecall straight from npm; nothing to host, nothing to sign up for.
How many people use Policyrecall?
The npm package @reneturcios/policyrecall was installed 274 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Policyrecall open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.