MCP Error Diagnosis

Full FREE body

Copy Back to MCP

Pack body is English. UI language controls translate chrome labels only.

### MCP Error Diagnosis
TYPE: MCP PRACTICAL RESOURCE
PURPOSE: Provide a reusable operational workflow for MCP Error Diagnosis that is specific to this job — not a cosmetic retitle of a generic MCP blurb.
PRECONDITION: Use the EXISTING BSV MCP implementation. Do not create a second MCP system. Do not assume a server, credential, transport, tool or permission exists unless verified.
INPUT: Intended use case; verified current configuration; required systems/data; current symptoms or desired outcome; security/permission constraints.
WORKFLOW:
1. Capture the symptom, expected behavior, and last known-good state.
2. Bisect across transport, auth, tool schema, and downstream system using verified facts.
3. Produce a hypothesis list ranked by likelihood; forbid invented logs.
4. Define reproducing steps and safe mitigations.
5. Write a short incident note: cause if known, fix, prevention.
Title-bound checklist for “MCP Error Diagnosis”:
- Restate success for error diagnosis in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute error diagnosis; reject unrelated material.
- Reference only verified MCP config while doing error diagnosis; never invent servers.
- Produce the artifact a practitioner would expect from error diagnosis.
- Self-check: does every claim serve error diagnosis? Remove filler.
- End with next verification specific to error diagnosis.
OUTPUT:
- Scope and success criteria for “MCP Error Diagnosis”
- Verified configuration notes (and explicit unknowns)
- Actionable checklist / workflow steps
- Risks, permissions, and residual gaps
- Verification / smoke checks
HOW TO USE: Copy into your notes or operator runbook and fill INPUT with real configuration. FREE COPY/USE — not a live RUN claim. Preserves the existing MCP shelf.
FREE: YES
PRIMARY ACTION: COPY / USE