Attestor MCP server
io.github.bolnet/attestor·v4.0.0·14 starsSelf-hosted memory for agent teams. Bi-temporal replay, deterministic retrieval, audit log.
14 stars
Reviews
Write oneNobody has reviewed Attestor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Attestor tools (4)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
memory_forgetArchive a specific memory by ID.
memory_getRetrieve a single memory by its ID.
memory_statsGet statistics about the memory store.
memory_timelineGet the chronological history of memories about an entity.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan103 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 9 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Attestor compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 68% of 4,464 AI and agents servers
- Tools
- 4
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 14
- more than 87% of 2,697 AI and agents servers
What its tools let an agent do: 4 read
Install Attestor in Claude Code, Cursor or VS Code
claude mcp add attestor -- uvx attestor
What the publisher says
From the Attestor repository's README, as published. We do not edit it. Read it on GitHub
Attestor
Governed memory for multi-agent production meshes.
Attestor is no longer "memory for your coding assistant." Three things happened: the editor vendors shipped memory for free, the benchmark race became a race about which LLM answers the question, and every serious conversation about a memory layer was about something else entirely: when many agents share one memory, who is allowed to write, who is allowed to forget, and can you prove it afterwards. So that is what Attestor is now.
When many agents share one memory, recall is the easy part. The hard part is who may write, who may forget, what an answer was built from, and whether you can prove all of it later. Attestor is a self-hosted memory service that makes those properties enforceable in code rather than in policy documents: role-based access at the AgentContext layer, provenance on every memory (optionally Ed25519-signed), per-agent token budgets and write quotas, a deterministic ranking path with no LLM in it, temporal supersession you can query as of any past moment, hard tenant isolation across all three storage roles, an auditable, audit-first forget-user path with declarative retention, and governance jobs that run as durable Temporal workflows: retried by policy, resumed after a crash, visible in an operator UI, and never on the read path. It runs as a Python library, a REST sidecar, or an MCP server with the same API. Role enforcement is an AgentContext guarantee and runs in process. The REST and MCP surfaces call the store directly and rely on their own auth.
ctx = AgentContext(agent_id="reviewer-1", role=AgentRole.REVIEWER, namespace="acme-prod")
ctx.add_memory("...") # PermissionError: REVIEWER lacks 'write'
mem.recall("...", context=ctx, as_of=last_friday) # what the mesh believed then — nothing is deletedpip install attestorDesigned and built by Surendra Singh — building auditable infrastructure for multi-agent AI, with fifteen years of production-systems discipline brought to the memory layer. Companion projects: claude-finance (Claude-powered financial analytics) · private-equity (PE × AI workshop). Reach out if you're hiring senior IC for AI infrastructure.
What it is
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Attestor: common questions
- Is Attestor MCP server safe?
- Mostly: it is graded B (83/100). Read the Attestor safety report
- How do I install Attestor?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Attestor need an API key?
- Yes. The registry entry asks for
OPENAI_API_KEY,OPENROUTER_API_KEY. - Is Attestor maintained?
- The last commit was 45 days ago (2026-09-18). The latest release is v4.0.0.
- What can I use instead of Attestor?
- Servers from other publishers that do the same job: Mnemoverse Memory MCP server, Total Agent Memory MCP server and three.ws Provenance MCP server. Compare all Attestor alternatives.
- How does Attestor compare with other AI and agents MCP servers?
- safety score 83/100 (higher than 68% of 4,464 AI and agents servers); tools 4 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Attestor
Same job from other publishers: the closest match first, then the best rated.
- Mnemoverse MemoryHosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcpnot reviewedEstablishedA
- Total Agent MemoryPersistent local memory for coding agents: temporal knowledge graph, procedural and episodic recallnot reviewedEstablishedA
- three.ws ProvenanceAppend-only, signed, on-chain-verifiable agent action log — record and audit what agents did.not reviewedEstablishedB
- adrkit decision memoryDeterministic, offline, read-only ADR decision memory for coding agents. No model or network calls.not reviewedEstablishedA
- Serena MCP: the IDE for your agentA powerful toolkit for coding, providing semantic retrieval and editing capabilities.not reviewedWidely usedC