LeashIndex Get the report

Index / data

io.github.YonasValentin/mcp-memory-graph

io-github-yonasvalentin-mcp-memory-graph declares 51 capabilities across 51 tools, with 2 critical issues.

92/100 exposureHigh exposure

Manifest recorded 2026-10-14 from tools/list answered by the npm package mcp-memory-graph@2.10.3 (published to npm as mcp-memory-graph, listed in the official MCP registry as io.github.YonasValentin/mcp-memory-graph 2.10.3), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 51 tools

51 of 51 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 4 of 51 tools

4 tools are classified as irreversible and declare no limit.

high · no-expiry · All 51 tools

51 of 51 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 51 tools

51 of 51 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 20 of 51 tools

20 tools can modify data and declare no limit.

low · uncapped-read · 27 of 51 tools

27 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
memory_storewrite assumed
memory_searchread declared
memory_getread declared
memory_updatewrite inferred
memory_deletedestructive declared
memory_listread declared
memory_ingestwrite assumed
memory_relatedread declared
memory_versionsread declared
memory_statsread declared
memory_verifyread declared
memory_tiersread declared
memory_exportread declared
memory_importdestructive declared
vault_syncwrite assumed
vault_statusread declared
vault_searchread declared
memory_export_vaultwrite inferred
memory_canvaswrite assumed
memory_consolidatewrite assumed
memory_extract_learningswrite assumed
memory_manifestread declared
memory_graphread declared
memory_extract_entitieswrite assumed
memory_condensewrite assumed
memory_restorewrite assumed
memory_queryread declared
core_memory_getread declared
core_memory_appendwrite assumed
core_memory_replacewrite assumed
memory_reflectwrite assumed
memory_communitiesread declared
memory_templateread declared
memory_session_notewrite assumed
memory_attributionread declared
memory_questionsread declared
memory_forgetdestructive declared
memory_historyread declared
memory_unlinked_mentionsread declared
memory_link_checkread declared
memory_query_structuredread declared
memory_version_diffread declared
memory_version_restoredestructive declared
memory_webhookwrite assumed
memory_insightsread declared
memory_healthread declared
memory_revalidatewrite assumed
memory_session_statewrite assumed
memory_expertisewrite assumed
memory_export_datasetread declared
memory_lessonwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.