Diagnose MCP connector failures by separating stored connection state from live upstream tool evidence.
Scanned 9/23/2026
Install to Claude Code
Skills Directorynpx -y skills add juanitourquiza/shipframe --skill mcp-debugging --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mcp Debugging?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/juanitourquiza-mcp-debugging)More formats (shields.io, HTML) on the badges page.
---
name: mcp-debugging
description: Diagnose MCP connector failures by separating stored connection state from live upstream tool evidence.
allowed-tools: Read Glob Grep Bash
argument-hint: '[--connector <name>]'
effort: medium
---
# MCP Debugging
Use when an MCP connector, tool, token, or upstream integration appears connected but behavior fails.
## Principles
- Stored connection state is not proof that the upstream service accepts the token/session.
- Prefer a live tool call or minimal endpoint check that exercises the failing capability.
- Capture exact error codes, tool names, timestamps, and sanitized payloads.
- Never expose secrets, tokens, cookies, or auth headers.
## Output
```markdown
## MCP Debug Report
**Connector:** <name>
**Claimed state:** <configured/active/unknown>
**Live check:** <command/tool and result>
**Root cause:** <best-supported cause or unknown>
**User action needed:** <reconnect, grant permission, rotate token, none>
**Evidence:** <sanitized snippets>
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
