Travel MCP Observatory: Core data
- Stichtag
- 23. Juli 2026
- Aktuelle MCP-Version
- 25 November 2025
- Release Candidate
- 2026-07-28; noch nicht final
- Messprinzip
- reproduzierbare Primärquellen
- Nicht gemessen
- Marktanteil ohne belastbare Grundgesamtheit
- Updateziel
- bei Spezifikationsänderung, mindestens quartalsweise
Current observation
As of 23 July 2026, protocol version 2025-11-25 remains the current published specification. The announced 2026-07-28 Release Candidate is a preview, not the normative baseline. Its proposed changes include a stateless core, a formal extension model, Tasks as an extension, MCP Apps, authorization hardening and a deprecation policy.
The observatory separates confirmed specification events, experimental capabilities and editorial monitoring topics. It avoids absolute ecosystem counts without a defensible population.
Method and reproducibility
Every indicator records observation unit, query time, primary source, extraction rule, normalization and evidence level. Repository stars, package downloads and registry entries may indicate activity, but they do not establish security, protocol conformance or production adoption.
Corrections create a new dated revision instead of silently rewriting the earlier observation. Architecture guidance is tested against the current specification; release candidates are evaluated separately as migration signals.
Research question and boundary
Travel MCP Observatory examines a methodologically transparent observatory for specifications, servers, travel standards, research and maturity indicators. The module distinguishes normative MCP requirements from editorial travel-architecture patterns. A pattern is not presented as protocol behaviour unless the versioned specification supports that claim.
The analysis also separates interoperability from suitability. A server may exchange valid MCP messages and still be unsafe, semantically ambiguous or unusable for a production travel process.
Travel-domain validity
Travel evidence must preserve the authoritative source, retrieval time, identifier namespace, currency, conditions and validity window. Offer, order, reservation, PNR, ticket, EMD and itinerary describe different states and must not be collapsed into a generic booking object.
For write operations, the test model includes repricing or state revalidation, object-level authorization, approval bound to the exact material terms, idempotency and recovery after a partial downstream failure. MCP supplies none of these domain guarantees automatically.
Method, falsification and evidence
The recorded indicators for this module include Stichtag: 23. Juli 2026; Aktuelle MCP-Version: 2025-11-25; Release Candidate: 2026-07-28; noch nicht final; Messprinzip: reproduzierbare Primärquellen; Nicht gemessen: Marktanteil ohne belastbare Grundgesamtheit; Updateziel: bei Spezifikationsänderung, mindestens quartalsweise. Each claim should identify its observation date and primary source. Release candidates, experimental capabilities and editorial inferences are labelled separately from the current protocol baseline.
A useful result must survive counterexamples: unsupported client capabilities, malformed or adversarial content, stale supplier state, denied authorization, timeout and duplicate execution. The evidence package combines contract tests, negative tests, trace correlation and a documented owner for corrections.
Interpretation for decision-makers
The module is not a product ranking or an assurance certificate. Registry presence, repository activity or a successful demonstration cannot prove security, legal authority, commercial access or operational maturity.
A decision should state which uncertainty the module reduced, which assumptions remain open and what would falsify the conclusion. This prevents an interactive graphic or catalogue entry from being mistaken for production due diligence.
Primary sources and academic context
This page follows the versioned MCP specification and separates normative requirements from architectural recommendations.