H/MMCP 2026

FREE LOCAL TOOL / LOCKED RELEASE-CANDIDATE MAP

The next MCP release removes the session you may still depend on.

Declare how your client or server behaves. Get a prioritized transition trace from stable 2025-11-25 to the locked 2026-07-28 release candidate.

MAP MY IMPLEMENTATION RC locked 2026-05-21. Final publication is expected 2026-07-28 and has not been verified by this tool.
STABLE2025.11SESSIONinitialize / Mcp-Session-Id
28 CHECKS
LOCKED RC2026.07STATELESSper-request context / discover
CODE_UPLOAD::0RUNTIME_TEST::0CLAIM::DECLARED
2025-11-25SOURCE BASELINE
2026-07-28LOCKED RC TARGET
28DETERMINISTIC CHECKS
LOCALDECLARATIONS STAY IN BROWSER

STEP 01 / IMPLEMENTATION CONTEXT

Describe the boundary, not the brand.

No project name, repository, endpoint or source code is requested. Context only decides which transition checks apply.

STEP 02 / DECLARED BEHAVIOR

Mark what the implementation does today.

Unknown is valid evidence. An unanswered check becomes an explicit gap instead of a guessed pass.

YESNOUNKNOWNN/A IS COMPUTED FROM CONTEXT
SYNTHETIC PROFILESDemonstrations only. Counted separately from manual assessments.
LOCAL DECLARATIONS / LOCAL HASH / SOURCE-MINIMIZED OUTPUTNo code, project name, repository, endpoint or credential is sent to H/M.

DECLARED READINESS / NOT RUNTIME CONFORMANCE

Migration control plane

SHA-256--

Unknowns belong in the map.

Answer only what you can support, then generate the transition order.

TRANSITION EVIDENCE, NOT A BADGE

Make protocol debt legible before changing code.

The lab converts declared implementation behavior into a deterministic queue. It does not inspect source, send protocol requests or run the official conformance suite.

  1. 01

    Scope applicability

    Transport and feature context remove checks that cannot apply.

  2. 02

    Preserve unknowns

    Missing evidence stays unknown instead of becoming a favorable assumption.

  3. 03

    Order migration

    Handshake, session, routing and authorization blockers precede improvements.

  4. 04

    Export minimally

    The report contains rule states and actions without identity or source material.

EXPLICIT RELEASE BOUNDARY

The target is a locked release candidate, not a verified final specification.

  • The final 2026-07-28 publication had not occurred as of this ruleset date and may differ.
  • No source code, dependency, traffic capture or endpoint is inspected.
  • No official SDK or conformance suite is executed.
  • Declared-ready means the selected answers match this published checklist; it is not compatibility certification.