Model Context Protocol
Stateless core, discovery, routing headers, cache metadata, authorization, tasks and deprecations.
/ quellen
Jede veränderliche Behauptung braucht eine datierte Primärquelle. Dieses Register zeigt, worauf der aktuelle Preview-Stand tatsächlich beruht.
Stateless core, discovery, routing headers, cache metadata, authorization, tasks and deprecations.
Explicit SDK opt-in, version negotiation and migration behavior.
OAuth-based authorization, protected-resource metadata, resource indicators, token audience validation and scope selection.
Threats and mitigations around token handling, confused deputy risks, local servers and authorization flows.
Tool discovery, schemas, annotations, invocation and human-in-the-loop guidance.
Official interactive development and inspection tool for MCP servers.
OAuth security best current practice, including redirect validation, code flow protection and token replay prevention.
Allowlisting, redirect handling, IP and DNS validation, protocol restrictions and network-layer defenses.
Hosted Streamable-HTTP endpoint, supported client paths, MCP key, account requirements and API-unit limits.
Read-only data access, supported assistants, OAuth or API key, plan scope and MCP API units.
v3 server, hosted and local modes, four tools, transports, OAuth and credential fallback; prior v2+ is deprecated.
Search, scrape, batch scrape, map and crawl tools, API-key setup, caching and standard API rate-limit boundary.
Hosted Streamable-HTTP endpoint, removed legacy SSE path, OAuth or token access, local stdio, Actors and operational tools.
Current public Keyword Database, Site Audit, Action Center, workspace and cost model. No public MCP claim observed.
Query dimensions, filters, aggregation, freshness and documented result limits for Search Analytics data.
Official SDK connection patterns for local stdio and remote Streamable HTTP transports.
Public remote-server URL requirements, Streamable HTTP preference and legacy SSE status.
Suchergebnis-Snippets, Drittanbieter-Listen, Marketingvergleiche ohne Methodik und gemeinsam betriebene Portfolioseiten gelten nicht als unabhängige Bestätigung. Interne Crawl-Foundry-Roadmaps belegen die Produktabsicht, aber nicht die öffentliche Verfügbarkeit.