LeashIndex Get the report

Index / devtools

CP Memory

io-github-cjhuochai-cp-memory declares 40 capabilities across 40 tools, with 2 critical issues.

83/100 exposureHigh exposure

Manifest recorded 2026-10-12 from tools/list answered by the PyPI package cp-memory-mcp==1.8.1 (published to PyPI as cp-memory-mcp, listed in the official MCP registry as io.github.CJhuochai/cp-memory 1.8.1), run in an isolated container with no network access and no 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 40 tools

40 of 40 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 · 1 of 40 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 40 tools

40 of 40 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 40 tools

40 of 40 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 · 19 of 40 tools

19 tools can modify data and declare no limit.

low · uncapped-read · 20 of 40 tools

20 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_schemaread inferred
memory_addwrite inferred
memory_personal_addwrite inferred
memory_personal_derivewrite assumed
memory_episode_consolidateread inferred
memory_personal_listread inferred
memory_personal_reviewread inferred
memory_review_digestread inferred
memory_review_inboxread inferred
memory_review_applywrite assumed
memory_correctwrite assumed
memory_personal_resolvewrite assumed
memory_searchread inferred
memory_proberead inferred
memory_explainread inferred
memory_inspectwrite assumed
memory_alias_addwrite inferred
memory_alias_listread inferred
memory_updatewrite inferred
memory_removedelete inferred
memory_listread inferred
memory_statsread inferred
memory_healthread inferred
memory_decision_addwrite inferred
memory_decision_listread inferred
memory_task_setwrite inferred
memory_task_getread inferred
memory_task_donewrite assumed
memory_workflow_savewrite assumed
memory_workflow_getread inferred
memory_workflow_listread inferred
memory_link_addwrite inferred
memory_link_listread inferred
memory_touchwrite assumed
memory_conflictsread inferred
memory_maintenancewrite assumed
memory_governance_reportwrite assumed
memory_auto_extract_cleanupread inferred
memory_restore_contextwrite assumed
memory_recallwrite 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.