Agent Recall (Goldentrii) MCP Server

agent-recall-mcp npm v3.4.47

Published by goldentrii — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Memory Palace MCP server for AI agents

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

Each tool and what it can reach — statically extracted from the published source.

  • checknetwork egress
  • alignment_checkno sensitive capability
  • awareness_updateno sensitive capability
  • check_actionno sensitive capability
  • context_synthesizeno sensitive capability
  • digestno sensitive capability
  • journal_archiveno sensitive capability
  • journal_captureno sensitive capability
  • journal_cold_startno sensitive capability
  • journal_listno sensitive capability
Show 27 more tools ↓
  • journal_projectsno sensitive capability
  • journal_readno sensitive capability
  • journal_rollupno sensitive capability
  • journal_searchno sensitive capability
  • journal_stateno sensitive capability
  • journal_writeno sensitive capability
  • knowledge_readno sensitive capability
  • knowledge_writeno sensitive capability
  • nudgeno sensitive capability
  • palace_lintno sensitive capability
  • palace_readno sensitive capability
  • palace_searchno sensitive capability
  • palace_walkno sensitive capability
  • palace_writeno sensitive capability
  • pipeline_closeno sensitive capability
  • pipeline_currentno sensitive capability
  • pipeline_listno sensitive capability
  • pipeline_openno sensitive capability
  • pipeline_showno sensitive capability
  • recallno sensitive capability
  • recall_insightno sensitive capability
  • register_ruleno sensitive capability
  • rememberno sensitive capability
  • session_endno sensitive capability
  • session_startno sensitive capability
  • smart_recallno sensitive capability
  • smart_rememberno sensitive capability

What this scan could not see

Versions 9

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.4.47 latest A 96/100 0 1.13.0 2026-09-05
v3.4.46 A 96/100 0 1.13.0 2026-08-30
v3.4.45 A 96/100 0 1.12.1 2026-08-20
v3.4.43 A 96/100 0 1.12.1 2026-08-18
v3.4.42 A 96/100 0 1.12.1 2026-08-13
Show 4 more versions ↓
v3.4.41 A 96/100 0 1.12.1 2026-08-03
v3.4.40 A 96/100 0 1.12.1 2026-07-28
v3.4.39 A 96/100 0 1.12.1 2026-07-27
v3.4.38 A 99/100 0 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/agent-recall-mcp/badge.svg)](https://mcptrustchecker.com/registry/agent-recall-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/agent-recall-mcp"><img src="https://mcptrustchecker.com/registry/agent-recall-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/agent-recall-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan agent-recall-mcp --online

Use the free API → How scoring works

Other implementations of Agent Recall 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Communication & Collaboration