Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/xxczaki/local-history-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/xxczaki/local-history-mcp/local-history)<a href="https://agentmods.dev/mcp/xxczaki/local-history-mcp/local-history"><img src="https://agentmods.dev/badge/mcp/xxczaki/local-history-mcp/local-history/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/xxczaki/local-history-mcp/local-history"><img src="https://agentmods.dev/badge/mcp/xxczaki/local-history-mcp/local-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
local-history scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"local-history": {
"command": "node",
"args": [
"dist/index.js"
],
"env": {
"LOG_LEVEL": "info"
},
"description": "Access Cursor Local History for data recovery and context awareness"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 12 lines scan A 1a1a086f0da0
local-history is an MCP server published in the GitHub repository xxczaki/local-history-mcp (16 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other mcp servers, from other repositories
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
toolradar
MCP server for Toolradar: recommend, search, compare and price software tools, with verified prices and real alternatives. No API key needed. Works with Claude, ChatGPT, Cursor, VS Code and any MCP client. Runs locally from the toolradar-mcp npm package. Needs 1 environment variable to run.
tiny-go-mcp
MCP server "tiny-go-mcp" as configured in kioie/tiny-go-mcp-server. Runs in Docker (ghcr.io/kioie/tiny-go-mcp:1.1.2).
github-actions
GitHub Actions MCP — view runs, read logs, re-run jobs, and manage CI/CD. Runs locally from the mcp-server-github-actions npm package.
mcp
Build, version, review, and export websites, web apps, and games from a conversation. Remote server at 2ools.app.