
UNITARES MCP server
io.github.cirwel/unitares·v3.6.0·5 starsAccountability infrastructure for long-running AI agents. Shared memory is a provenance graph.
not scanned yet
5 stars
Reviews
Write oneNobody has reviewed UNITARES yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
UNITARES tools
No tool declarations could be read from the package source. They show once the server is installed.
How UNITARES compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
- GitHub stars
- 5
- more than 83% of 28,688 servers
Release history: 3 versions in the registry since 2026-10-08, latest 2026-10-26, typically one every 15 days.
Install UNITARES in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the UNITARES repository's README, as published. We do not edit it. Read it on GitHub
Accountability infrastructure for long-running AI agents.
Give every process an identity. Keep claims, evidence, reviews, and outcomes connected. Recover work across restarts, context loss, and handoffs.
An agent reports that its fix is done and the tests pass. By morning its session has restarted, its context is gone, and another process has taken over the task. Who said it? What supports it? Who challenged it? What happened? Each run leaves its own log, and the answers scatter across them.
UNITARES is self-hosted accountability infrastructure for operators running multiple AI agents. Its single-operator federation kernel connects independent runtimes to one operator-controlled server over MCP or HTTP, where they share a durable record while keeping their own models, tools, and runtimes. They interoperate with each other over their own transports or A2A; UNITARES is the record behind them, not the transport between them.
UNITARES preserves accountability across discontinuities in agent identity, context, process, and time. Agent work remains attributable, reviewable, and recoverable even when the process that started it is gone.
What UNITARES gives you
came from. This is a record for attribution, not a credential; platform workload identity remains the credential layer.
- Identity and lineage — know which process acted and where inherited work
provenance outside any one context window.
- Claims and evidence — retain important findings, corrections, and their
part of the work record.
- Governed review — preserve disagreement, conditions, and resolution as
happened.
- Outcome grounding — connect predictions and check-ins to what later
checkpoints in an agent's loop.
- Runtime policy — return an action, reason, and next step at meaningful
continue earlier work.
- Reconstruction — give a successor the records needed to understand and
The claim ledger gives the evidence status of each measured result.
Together, these form an operator-owned accountability layer across coding agents, research agents, background agents, and custom runtimes. What it adds to a record of what happened is adjudication: disagreement, conditions, and outcomes bound to the process that made the claim.
Install
With Git, curl, and Docker Compose installed, one command starts the latest verified release of the local operator stack:
v=$(curl -fsSL https://raw.githubusercontent.com/cirwel/unitares/master/PUBLISHED_VERSION) && git clone --branch "v$v" --depth 1 https://github.com/cirwel/unitares.git && cd unitares && docker compose up -d --waitConnect MCP clients at http://localhost:8767/mcp/ or open the dashboard at http://localhost:8767/dashboard. If port 8767 or 8788 is taken, set GOVERNANCEHOSTPORT and LEASEPLANEHOST_PORT; see Docker quickstart.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
UNITARES: common questions
- Is UNITARES MCP server safe?
- Mostly: it is graded B (70/100). Read the UNITARES safety report
- Does UNITARES need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is UNITARES maintained?
- The last commit was 26 days ago (2026-10-09). The latest release is v3.6.0.
- What can I use instead of UNITARES?
- Servers from other publishers that do the same job: Codebase Memory MCP server, Neo4j Memory MCP server and Nautilus Compass Memory MCP server. Compare all UNITARES alternatives.
- How does UNITARES compare with other MCP servers?
- safety score 70/100 (higher than 35% of 48,255 servers); github stars 5 (more than 83% of 28,688 servers). Full comparison.
Alternatives to UNITARES
Same job from other publishers: the closest match first, then the best rated.
- Codebase MemoryCodebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.not reviewedWidely usedC
- Neo4j MemoryMCP Neo4j Knowledge Graph Memory Servernot reviewedEstablishedA
- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB
State Memory MCPPersistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.not reviewedEstablishedA