MCP Connection QA

Full FREE body

Copy Back to MCP

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

### MCP Connection QA
TYPE: MCP PRACTICAL RESOURCE
PURPOSE: Provide a reusable operational workflow for MCP Connection QA 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. Define the exact operational outcome required by “MCP Connection QA”.
2. Use only verified MCP configuration; mark unknowns.
3. Apply least privilege and avoid inventing servers/tools/credentials.
4. Produce a practical checklist or workflow the operator can follow.
5. State verification steps and residual gaps.
Title-bound checklist for “MCP Connection QA”:
- Restate success for connection qa in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute connection qa; reject unrelated material.
- Reference only verified MCP config while doing connection qa; never invent servers.
- Produce the artifact a practitioner would expect from connection qa.
- Self-check: does every claim serve connection qa? Remove filler.
- End with next verification specific to connection qa.
OUTPUT:
- Scope and success criteria for “MCP Connection QA”
- 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