Protocol watch
MCP 2026-07-28
Official specification change · checked 6 September 2026The current tracked specification is materially different from 2025-11-25: it removes protocol-level sessions and the initialize handshake, adds server/discover, changes subscription handling, and moves tasks into an extension.
Review impact: connection, transport, discovery and authorization cases must be version-specific. A passing legacy handshake does not establish compatibility with the 2026-07-28 protocol.
Official key changesPublished releases
01Commercial operating scope
Founding evidence pilot v1.0
Published a paid pilot boundary for authorized real-world evidence without broad access or pre-execution compatibility claims.
- Kept the existing US$495 scope and payment schedule rather than inventing an untested price.
- Defined eligibility, scope ceilings, authorization gates, stop conditions and private-by-default evidence handling.
- Set every pre-execution result to UNKNOWN and made public identification or findings a separate post-delivery opt-in.
02Executed workflow evidence
Workflow harness v0.2
Executed a six-step discover, search, read, cite and deny sequence against a disposable local fixture.
- Verified discovery-before-use and search-result propagation into the read request.
- Verified citation text and source against the returned document, plus a denied-role negative path.
- Published a separate run without rewriting the earlier blocked workflow; no named MCP client or customer system was involved.
03Traceability model
Evidence graph v1.0
Linked the local run from versioned context through permissions and cases to its exact evidence artifacts.
- Published 24 typed nodes and 29 relationships for the local demonstration run.
- Represented the absent named client explicitly and kept the blocked workflow without an artifact edge.
- Linked the run, contract, fixture, environment, authorization, permissions, manifest, bundle, mark and monitoring record.
04Freshness ledger
Evidence monitoring v1.0
Published a dated observation ledger that keeps test outcome separate from evidence age.
- Defined CURRENT, STALE, EXPIRED, UNVERIFIABLE and NO RESULT without changing the underlying test outcome.
- Set a 14-day current window and a fixed expiry tied to the existing evidence mark.
- Disclosed that this first ledger has one observation and no automatic scheduler, alerting or customer target.
05Evidence label
Scoped evidence mark v1.0
Issued a narrow, expiring mark for the local harness run without presenting it as certification or approval.
- Bound the mark to one fixture, contract, environment, run and set of case IDs.
- Kept the overall result FAIL because one executed assertion failed; the blocked workflow remains separate.
- Added evidence hashes, automatic expiry and explicit unverifiable, superseded and revoked states.
06Executed proof of method
Local evidence harness v0.1
Ran a versioned contract against a disposable loopback fixture and published the resulting evidence bundle.
- Five local requests executed: four PASS and one deliberately seeded FAIL.
- One workflow remains BLOCKED with a recorded missing prerequisite and no execution artifact.
- Published redacted JSON evidence, per-file hashes, source/environment provenance and explicit non-MCP limitations.
07Evidence model
Compatibility matrix v0.1
Published the first server–client matrix without converting documentation overlap into compatibility evidence.
- Added a Codex × Sourcegraph MCP Server case matrix.
- All eight unexecuted cases remain UNKNOWN.
- Added a persistent result model where BLOCKED requires a recorded blocker and public visibility is explicit.
08Public reference profile
Client profile format v0.1
Published the first version-bounded MCP client profile using official publisher documentation.
- Added a sourced Codex client profile.
- Separated documented features from executed server-pairing evidence.
- Kept the installed build, negotiated protocol, authentication outcome and workflow result explicitly unknown.
09Operating standard
Legal & operating foundation v1.0
Published a clearer pre-engagement legal and safety boundary before accepting customer access or payment.
- Expanded service terms and the POPIA privacy notice.
- Added engagement authorization and credential/evidence handling procedures.
- Clarified the US$495 wording, refund boundary, IP, confidentiality, liability and descriptive use of MCP.
010Public reference profile
Server profile format v0.1
Published the first server profile using official documentation while keeping vendor claims separate from independent test evidence.
- Added a sourced Sourcegraph MCP Server profile.
- Marked independent testing as not performed.
- Recorded unknowns instead of inferring protocol-version or deployment-level compatibility.
011Review standard
Taxonomy v0.1
Published eleven stable case families and rules connecting scope, environment, results and evidence.
- Added CON, TRN, AUT, DSC, TOL, ERR, CLI, WRK, ENT, PRF and SAF families.
- Defined PASS, FAIL, BLOCKED, UNKNOWN and NOT APPLICABLE without turning catalogue entries into executed coverage.
- Made named-client and workflow checks distinct from scripted protocol requests.
012Review standard
Methodology v1.0
Published the authorization, execution, interpretation, evidence, data-handling and re-test procedure.
- Requires a written boundary and stop conditions before testing.
- Requires exact versions and dated sources; unknowns remain visible.
- Clarifies that the review is not certification, security assurance or a guarantee of platform approval.
013Demonstration asset
Sample report 2.1
Replaced the earlier public report with a fictional local fixture and a traceable evidence bundle.
- Five local requests captured: four pass the local contract and one deliberately seeded case fails.
- One workflow remains BLOCKED with no execution artifact.
- Redesigned the report and removed personal attribution from customer-facing presentation.
No hidden history
What is not in this log.
No customer review, external server test, named-client compatibility result, paid engagement, continuous monitor or certification has been completed or claimed here. When a real, authorized result is publishable, its scope and permission to disclose must be recorded before it appears.