Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/matt-dionis/claude-code-configs/mcp-debuggit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/matt-dionis/claude-code-configs/mcp-debug)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/mcp-debug"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/mcp-debug.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00008 | $0.00698 |
| Opus 5 | $0.00004 | $0.00349 |
| Sonnet 5 | $0.00002 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade B, and why
mcp-debug scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
cat .mcp.json How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory MCP Server Debugging
Debug the Memory MCP server implementation with focus on $ARGUMENTS:
1. Server Initialization & Configuration
- Verify MCP server startup and registration
- Check @modelcontextprotocol/sdk initialization
- Validate server manifest and capabilities
- Test stdio/HTTP transport configuration
- Verify database connection (Neon PostgreSQL)
2. MCP Protocol Compliance
- Validate JSON-RPC 2.0 message format
- Test request/response correlation (id matching)
- Verify error response format (code, message, data)
- Check notification handling (no id field)
- Validate batch request support
3. Memory Tool Registration
- Verify tool discovery and registration:
create_memory- Memory creation with embeddingssearch_memories- Vector similarity searchget_memory- Direct retrievalupdate_memory- Memory updatesdelete_memory- Soft/hard deletionlist_memories- Pagination support
- Validate tool parameter schemas (Zod validation)
- Test tool permission boundaries
4. Database & Vector Operations
- Test pgvector extension functionality
- Verify embedding generation (OpenAI API)
- Debug vector similarity search queries
- Check index usage (IVFFlat/HNSW)
- Validate transaction handling
5. Session & Authentication
- Debug companion session management
- Verify user context isolation
- Test multi-tenancy boundaries
- Check session persistence
- Validate auth token handling
6. Error Handling & Recovery
- Test database connection failures
- Handle embedding API errors
- Verify graceful degradation
- Check error logging and telemetry
- Test retry mechanisms
7. Performance & Memory Leaks
- Monitor connection pooling
- Check for memory leaks in long sessions
- Verify streaming response handling
- Test concurrent request handling
- Profile vector search performance
8. Common Issues & Solutions
Connection Refused
# Check if server is running
ps aux | grep "memory-mcp"
# Verify port binding
lsof -i :3000
# Test direct connection
npx @modelcontextprotocol/cli connect stdio "node ./dist/index.js"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 116 lines · 8 tokens per session scan B a572c2c3cdfa
mcp-debug is a command published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 698 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.