MCP glossary knowledge graph: Core data

Knotenklassen
Protokoll, Travel, Sicherheit, Daten, Betrieb
Relationen
ist-ein, verwendet, exponiert, autorisiert, liefert, begrenzt
Normative Basis
MCP 2025-11-25
Darstellung
filterbarer lokaler Graph

Explore the graph

Filter protocol, travel, security and data concepts. Every edge has direction and a named meaning.

Terminology governance

Every concept records preferred label, synonyms, definition, source, scope, version and review date.

Research question and boundary

MCP glossary knowledge graph examines a terminologically controlled knowledge graph connects MCP concepts with travel entities, standards and security concepts. 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 Knotenklassen: Protokoll, Travel, Sicherheit, Daten, Betrieb; Relationen: ist-ein, verwendet, exponiert, autorisiert, liefert, begrenzt; Normative Basis: MCP 2025-11-25; Darstellung: filterbarer lokaler Graph. 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.