Memoryrelay MCP Server
@memoryrelay/mcp-server
npm
v0.4.1
Published by @memoryrelay — 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.
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:
| Points | Adoption-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 1
medium Unconstrained URL/host parameter "webhook_url" on "memory_store_async"MTC-CAP-007
Tool "memory_store_async" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool memory_store_async · inputSchema.properties.webhook_url
Tools 44
Each tool and what it can reach — statically extracted from the published source.
memory_store_asyncnetwork egressagent_createno sensitive capabilityagent_getno sensitive capabilityagent_listno sensitive capabilitycontext_buildno sensitive capabilitydecision_checkno sensitive capabilitydecision_listno sensitive capabilitydecision_recordno sensitive capabilitydecision_supersedeno sensitive capabilityentity_createno sensitive capability
Show 34 more tools ↓
entity_graphno sensitive capabilityentity_linkno sensitive capabilityentity_listno sensitive capabilitymemory_batch_storeno sensitive capabilitymemory_contextno sensitive capabilitymemory_deleteno sensitive capabilitymemory_forgetno sensitive capabilitymemory_getno sensitive capabilitymemory_healthno sensitive capabilitymemory_listno sensitive capabilitymemory_promoteno sensitive capabilitymemory_recallno sensitive capabilitymemory_searchno sensitive capabilitymemory_statusno sensitive capabilitymemory_storeno sensitive capabilitymemory_updateno sensitive capabilitypattern_adoptno sensitive capabilitypattern_createno sensitive capabilitypattern_searchno sensitive capabilitypattern_suggestno sensitive capabilityproject_add_relationshipno sensitive capabilityproject_contextno sensitive capabilityproject_dependenciesno sensitive capabilityproject_dependentsno sensitive capabilityproject_impactno sensitive capabilityproject_infono sensitive capabilityproject_listno sensitive capabilityproject_registerno sensitive capabilityproject_relatedno sensitive capabilityproject_shared_patternsno sensitive capabilitysession_endno sensitive capabilitysession_listno sensitive capabilitysession_recallno sensitive capabilitysession_startno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.4.1 latest |
A 96/100 | 1 | 1.9.0 | 2026-07-24 |
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.
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 @memoryrelay/mcp-server --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.