LeashIndex Get the report

Index / storage

io.github.carloshpdoc/memorydetective

io-github-carloshpdoc-memorydetective declares 42 capabilities across 42 tools, with 1 critical issue.

77/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package memorydetective@1.18.1 (published to npm as memorydetective, listed in the official MCP registry as io.github.carloshpdoc/memorydetective 1.18.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 42 tools

42 of 42 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.

high · no-expiry · All 42 tools

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

42 of 42 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 · 16 of 42 tools

16 tools can modify data and declare no limit.

low · uncapped-read · 26 of 42 tools

26 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
analyzeMemgraphread inferred
findCyclesread inferred
findRetainersread inferred
countAliveread inferred
diffMemgraphswrite assumed
analyzeAbandonedMemoryread inferred
cleanupTraceswrite assumed
classifyCyclewrite assumed
analyzeHangsread inferred
analyzeTimeProfileread inferred
listTraceDevicesread inferred
listTraceTemplatesread inferred
inspectTracewrite assumed
summarizeTracewrite assumed
recordTimeProfilewrite assumed
captureMemgraphwrite assumed
bootAndLaunchForLeakInvestigationwrite assumed
replayScenariowrite assumed
captureScenarioStatewrite assumed
analyzeAnimationHitchesread inferred
analyzeAllocationsread inferred
analyzeAppLaunchread inferred
analyzeNetworkActivityread inferred
analyzeMemoryFootprintread inferred
analyzeEnergyImpactread inferred
analyzeLeakTimelineread inferred
recordViaInstrumentsAppwrite assumed
analyzeMetricKitPayloadread inferred
renderCycleGraphwrite assumed
logShowread inferred
logStreamwrite assumed
detectLeaksInXCUITestwrite assumed
detectLeaksInXCTestwrite assumed
reachableFromCyclewrite assumed
swiftGetSymbolDefinitionread inferred
swiftFindSymbolReferencesread inferred
swiftGetSymbolsOverviewread inferred
swiftGetHoverInforead inferred
swiftSearchPatternread inferred
getInvestigationPlaybookread inferred
verifyFixread inferred
compareTracesByPatternread inferred
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.