MCP Server Evaluation

Full FREE body

Copy Back to MCP

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

### MCP Server Evaluation
TYPE: MCP PRACTICAL RESOURCE
PURPOSE: Provide a reusable operational workflow for MCP Server Evaluation 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 evaluation criteria for the MCP server/tool decision (capability, reliability, permission surface, ops cost).
2. Score only candidates evidenced in supplied materials; mark unknowns.
3. Compare failure modes and operational burden, not marketing claims.
4. Recommend adopt/trial/reject with explicit reasons.
5. List validation experiments before production reliance.
Title-bound checklist for “MCP Server Evaluation”:
- Restate success for server evaluation in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute server evaluation; reject unrelated material.
- Reference only verified MCP config while doing server evaluation; never invent servers.
- Produce the artifact a practitioner would expect from server evaluation.
- Self-check: does every claim serve server evaluation? Remove filler.
- End with next verification specific to server evaluation.
OUTPUT:
- Scope and success criteria for “MCP Server Evaluation”
- 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