### MCP Production Review TYPE: MCP PRACTICAL RESOURCE PURPOSE: Provide a reusable operational workflow for MCP Production Review 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 production readiness gates for the MCP use case. 2. Check auth, rate limits, idempotency, observability, and rollback using supplied config. 3. Draft a runbook: health checks, common failures, escalation. 4. List metrics/logs that must exist before calling it production-ready. 5. Call out anything still untested. Title-bound checklist for “MCP Production Review”: - Restate success for production review in one measurable sentence (or mark unmeasurable). - List the minimum inputs required to execute production review; reject unrelated material. - Reference only verified MCP config while doing production review; never invent servers. - Produce the artifact a practitioner would expect from production review. - Self-check: does every claim serve production review? Remove filler. - End with next verification specific to production review. OUTPUT: - Scope and success criteria for “MCP Production Review” - 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 --- Source: https://botshelfvampire.com/library/mcp/mcp-production-review/ License: MIT (original BSV text). Use at your own risk.