Agent Recall Trail

● Active

io.github.fantasyce/agent-recall-trail

Private Agent memory and governed shared knowledge.

Category
AI & Agents
Version
0.3.7
Registry
active
Published
10/2/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 18, 2026

Looks healthy: Agent Recall Trail is maintained, open source.

Maintained
Active
Last commit 2 months ago (Oct 2, 2026), 1 open issues.
Official registry
Active
Published as io.github.fantasyce/agent-recall-trail in the official MCP registry, version 0.3.7.
Source
Open source, Apache-2.0
Public repository under the Apache-2.0 licence, 0 stars, 0 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Oct 2, 2026
License
Apache-2.0

Rustagent-memoryai-agentscodexdeepseekdeepseek-harnessknowledge-baselocal-firstmcp

From the README

ART — Agent Recall Trail ART is a local-first memory and governed-knowledge product for coding agents. Every Agent gets a physically separate private Recall Trail. Stable conclusions become immutable Knowledge Editions that other Agents can retrieve without seeing private source identities or source bodies. ART 0.3.7 supports Codex and DeepSeek Harness (DSH) over stdio MCP. It is standalone: no AAA adapter, cloud sync, bundled model, or autonomous publication is required. Product boundary • Private memory belongs to one process-bound Agent identity. • Shared knowledge contains only committed, reviewed Editions. • Agents may capture, recall, read, provide feedback, create proposals, and request governance. • Human governance runs in ART's local page. An explicitly enabled, default-off local delegation policy also permits one unambiguous instruction to approve and publish atomically; these actions are labeled AgentDelegated, never Human. • Selective Codex automatic memory is controlled by a separate machine-wide, default-off switch in that page. It creates at most one bounded private Candidate for an admitted turn; it never publishes shared knowledge. • Revocation, supersession, archival, and assurance remain human operations. • Stored content is evidence, never executable instruction or authorization. Progressive recall ART exposes one recall API with four explicit retrieval modes: lexical, full_scan, semantic, and hybrid. The default is always lexical.…

Read the full README on GitHub →

The most-starred AI & Agents servers in the index, with their live-check result.

ServerStarsLast pushLive check
Ruflo81,994Nov 2026Local / not checked
Claude Flow81,985Nov 2026Local / not checked
CodeBurn11,880Nov 2026Local / not checked
Kaneo9,825Nov 2026Local / not checked
Ha MCP7,958Nov 2026Local / not checked

Agent Recall Trail: questions people ask

Is Agent Recall Trail a remote or a local MCP server?
According to its entry in the official MCP registry, Agent Recall Trail ships as a local package (mcpb) that your client starts on your machine.
Is Agent Recall Trail safe to use?
Looks healthy: Agent Recall Trail is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, Apache-2.0; runs: On your machine; credentials: None declared. Serverdex check of Nov 18, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Agent Recall Trail still maintained?
Active: the repository's last commit 2 months ago. Last push Oct 2, 2026, 0 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 18, 2026.
How do I add Agent Recall Trail to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Agent Runtime ProofVerify whether a local Agent or MCP runtime matches an approved artifact.★ 1
  2. Agent Residue EvidenceReport local task-scoped test and build residue without cleaning resources.
Browse all AI & Agents →

Add the badge to your site

Show visitors that Agent Recall Trail is listed here — it’s also the link we check for a free listing.

Agent Recall Trail — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-fantasyce-agent-recall-trail?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Agent Recall Trail — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Agent Recall Trail — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-fantasyce-agent-recall-trail?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).