Skip to content

Model Context Protocol

MCP defines how tools, resources, prompts, and transports are exposed to AI clients.

Upstream references

What upstream owns

  • protocol messages
  • transport behavior
  • authorization specification
  • SDK APIs

What VCQA owns

  • tool safety rubric.
  • remote authorization policy.
  • tool schema quality.
  • auditability.

Detection signals

  • @modelcontextprotocol/sdk dependency
  • MCP server entrypoints
  • tool/resource schema definitions

Composed standards

Combination-born guidelines

  • MCP plus Workers requires edge authorization and protected resource metadata.
  • MCP plus Zod requires precise tool schemas that constrain arguments before execution.
  • MCP plus OAuth requires tool-level permission boundaries and audit trails for mutations.