Memorydetective

Name: Memorydetective
Author: carloshpdoc

memorydetective · by carloshpdoc

MCP server for iOS leak hunting and performance investigation. 28 MCP tools, 34-pattern retain-cycle classifier with Swift fixTemplate snippets, compareTracesByPattern for CI gating, SourceKit-LSP source bridging. Reads .memgraph and .trace files; macOS only.

11 109/wk 19 tools GitHub npm

No known CVEs

Apache-2.0 license

Maintained

Last commit 34d ago

Works with most clients

Transport: stdio, sse, http

19 tools · ~1.5k tok

Grade B · 0.7% of 200K ctx

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "memorydetective": {
      "args": [
        "-y",
        "memorydetective"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/memorydetective)](https://mcppedia.org/s/memorydetective)

Read me

What Memorydetective does

Diagnose iOS retain cycles and performance regressions from your chat window. No Xcode required.

Test This Server

This server supports HTTP transport. Be the first to test it — help the community know if it works.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

79/100across 5 weighted dimensions

How we score →

0255075100

−21

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked memorydetective against OSV.dev.

Inventory

Tools (19)

Click any tool to inspect its schema.

~1.5k tokens total

Inventory

Prompts (1)

summarize-trace

Summarize an xctrace trace with performance metrics and diagnostics

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Memorydetective safe to use?: Memorydetective has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install Memorydetective?: Memorydetective supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can Memorydetective do?: Memorydetective provides 19 tools: analyzeMemgraph, classifyMemgraph, inspectTrace, summarizeTrace, recordTimeProfile and 14 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Memorydetective?: Memorydetective is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is Memorydetective actively maintained?: Memorydetective is recently maintained — last commit was 34 days ago. It has 11 GitHub stars.

Similar servers

Others in other

View all →

Pi Lean Ctx95

Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.

3.0k 6

io.github.asklokesh/loki-mode94

Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.

992 8

Sigmap94

97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server

531 6

Sunpeak93

App framework, testing framework, and inspector for MCP Apps.

193 1

MCP Security Weekly

Get CVE alerts and security updates for Memorydetective and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Highlights

CLI-driven leak hunting. Read .memgraph files captured by Xcode (or by memorydetective itself on simulators), find ROOT CYCLEs, classify them against known SwiftUI/Combine patterns, and get a one-liner fix hint. All from a script or a chat.

MCP-native. Plugs into Claude Code, Claude Desktop, Cursor, Cline, and any other MCP client. The agent drives the full investigate → classify → suggest-fix loop without you opening Instruments.

Honest about its limits. No mocked outputs, no over-promises. Hangs analysis works clean from xctrace; sample-level Time Profile is parsed when xctrace symbolicates the trace and returns a structured workaround notice when it can't (the underlying xctrace SIGSEGV on heavy unsymbolicated traces is an Apple-side limitation we surface explicitly). Memory Graph capture works on Mac apps and iOS simulator; physical iOS devices still need Xcode.

What's new in v1.18 (2026-05-17): MetricKit + audit-close. analyzeMetricKitPayload is the 42nd MCP tool: ingests Apple MetricKit .mxdiagnostic JSON payloads from real-device TestFlight / App Store builds (post-mortem production diagnostics, no MCP competitor covers this lane today). Three actionable outputs: crash clusters by exception type / binary / top frame, hang hotspots with localized-duration parsing ("5.4 sec" / "20秒"), CPU + disk exceptions. Cross-tool chain hints (e.g. objc_release-style top frame surfaces a findCycles suggestion). Plus three audit-close items: open-enum SupportStatusKind (downstream consumers add kinds without a breaking type bump), invocation-scoped schemaDiscovery cache (summarizeTrace end-to-end shaved from ~28s to ~15s on real Apple traces via single up-front TOC fetch), and local-only integration tests against real Apple .trace bundles (closes the v1.14 P+O drift class for good). 701 → 757 tests. 41 → 42 MCP tools.

Also recent (v1.17): reliability pass. 14 bug fixes across three tiers. Headlines: strtobool env truthy parsing, verifyFix whitelist match modes (exact / substring / regex), recordViaInstrumentsApp catches traces saved outside watchDir, inspectTrace fault-tolerant fallback, configurable countAlive framework-noise filter, variable-size class min/max/median.

And v1.16: macOS 26.x recording-unblock release. New recordViaInstrumentsApp MCP tool wraps the Instruments.app GUI flow: opens the app, surfaces step-by-step instructions, watches a directory for the saved .trace, and chains into inspectTrace on success. Until Apple fixes the xcrun xctrace record regression on macOS 26.x sims, this is the automated path.

And v1.15: schema coverage + verify-fix UX. Three new MCP trace tools filled the remaining schema gap: analyzeMemoryFootprint (38th, VM resident / dirty / virtual + jetsam diagnosis), analyzeEnergyImpact (39th, battery drain investigation), analyzeLeakTimeline (40th, xctrace's leaks instrument as a time series). summarizeTrace now chains analyzeNetworkActivity. replayScenario captures simulator screens

Frequently Asked Questions

Is Memorydetective safe to use?

Memorydetective has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.

How do I install Memorydetective?

Memorydetective supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can Memorydetective do?

Memorydetective provides 19 tools: analyzeMemgraph, classifyMemgraph, inspectTrace, summarizeTrace, recordTimeProfile and 14 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with Memorydetective?

Memorydetective is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is Memorydetective actively maintained?

Memorydetective is recently maintained — last commit was 34 days ago. It has 11 GitHub stars.

Highlights