MCP Runtime Verification Guide

The release-critical path from implemented ingress to proven transport.

The canonical deployed MCP function URL is displayed because it is runtime verified. Bearer tokens remain one-time secrets and are represented only by a placeholder in client examples.
Step 1 of 4

Review Boundary

Separate implementation from runtime proof

Start with the current evidence boundary, not the marketplace. MCP ingress is now live-verified through the deployed Base44 function for the isolated `probe.increment` proof tool; external-provider enforcement is still uncertified.

Bounded runtime verification complete
  • Stateless MCP protocol `2026-07-28` is implemented in source.
  • Credential-derived identity and guarded execution are live verified.
  • Canonical deployed endpoint + external MCP client proof are reconciled.
  • External-provider enforcement and production certification remain pending.
View enforcement boundary