agent-recall
agent-recall is an MCP server published by Goldentrii, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does agent-recall support the current MCP specification (2026-07-28)?
Not yet confirmed. agent-recall is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is agent-recall a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for agent-recall (as of 2026-08-20).
How do I connect to agent-recall?
agent-recall is available via the package npm:agent-recall-mcp, the official MCP Registry under io.github.Goldentrii/agent-recall, the source repository at https://github.com/goldentrii/agentrecall-mcp. Authentication: unknown. Transports: stdio.
Does agent-recall support MCP revision 2025-11-25?
Yes. agent-recall supports MCP revision 2025-11-25 (checked 2026-08-20).
Does agent-recall support MCP revision 2026-07-28?
No. agent-recall was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were agent-recall's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
Which MCP spec revisions does agent-recall support?
agent-recall has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is agent-recall?
Ranked #201 in The MCP 500 with Adoption Index 50.90 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 218 | API · |
| GitHub stars | 371 | API · |
| GitHub forks | 58 | API · |
| Last push | 2026-09-13T00:12:03Z | API · |
| Repository archived | no | API · |
Repository and package signals for agent-recall
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 27
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Declared topics: agent-learning, agent-memory, ai-memory-systems, claude-code, claude-mcp, correction-tracking, mcp-server, memory-palace, persistent-memory, typescript — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
3.4.46- Last published
- First published
- Releases
- 84
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 236 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.Goldentrii/agent-recall at version 3.4.31 - lists package npm:agent-recall-mcp and repository https://github.com/goldentrii/agentrecall-mcp - accessed
- npm registry metadata for agent-recall-mcp at published version 3.4.45, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed