From 388956de0795b9ad4086a14289e2c79087d6aae0 Mon Sep 17 00:00:00 2001 From: Ming Wen Date: Wed, 19 Aug 2026 10:01:10 +0800 Subject: [PATCH 1/2] =?UTF-8?q?docs(readme):=20MCP=20gateway=20serves=20bo?= =?UTF-8?q?th=20protocol=20generations=20=E2=80=94=202026-07-28=20stateles?= =?UTF-8?q?s=20+=20per-server=20pin?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fa9305b5a..87846db23 100644 --- a/README.md +++ b/README.md @@ -179,8 +179,13 @@ Covered by 183 end-to-end scenario files (496 cases) that run against real gatew callers get provider-side prompt discounts without changing their requests. - **MCP gateway** — register upstream MCP servers as first-class resources and front them all behind one endpoint (`/mcp`), with the gateway holding each server's upstream - credential, namespacing tools per server, and enforcing per-caller tool access. Also - exposes a REST API as MCP tools from its OpenAPI description. + credential, namespacing tools per server, and enforcing per-caller tool access. Serves + every current MCP protocol revision — `2025-03-26` through the stateless `2026-07-28` — + negotiated per client with no sessions to pin, and connects upstream per server via the + `initialize` handshake or, with `protocol_version: "2026-07-28"`, handshake-free + `server/discover` for servers that no longer answer `initialize`. The tool surface is + validated against the official MCP conformance suite in CI. Also exposes a REST API as + MCP tools from its OpenAPI description. - **A2A agent gateway** — front A2A (Agent-to-Agent) agents at `/a2a/:agent`, serving each agent's card with URLs rewritten to the gateway, over JSON-RPC 2.0. - **Inbound authentication** — caller API keys (SHA-256 hashed, model allowlists, expiry, From 1a0ca03d18af240be392dc4bded7e02e00737512 Mon Sep 17 00:00:00 2001 From: Ming Wen Date: Wed, 19 Aug 2026 10:22:00 +0800 Subject: [PATCH 2/2] =?UTF-8?q?docs(readme):=20tighten=20the=20MCP=20bulle?= =?UTF-8?q?t=20per=20review=20=E2=80=94=20precise=20revision=20phrasing,?= =?UTF-8?q?=20scoped=20conformance=20claim?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 87846db23..758aaf5ec 100644 --- a/README.md +++ b/README.md @@ -177,15 +177,12 @@ Covered by 183 end-to-end scenario files (496 cases) that run against real gatew memory and Redis backends; cost-saved telemetry on every hit. Separately, **automatic prompt caching** can be enabled per direct Anthropic model to inject cache breakpoints, so callers get provider-side prompt discounts without changing their requests. -- **MCP gateway** — register upstream MCP servers as first-class resources and front them - all behind one endpoint (`/mcp`), with the gateway holding each server's upstream - credential, namespacing tools per server, and enforcing per-caller tool access. Serves - every current MCP protocol revision — `2025-03-26` through the stateless `2026-07-28` — - negotiated per client with no sessions to pin, and connects upstream per server via the - `initialize` handshake or, with `protocol_version: "2026-07-28"`, handshake-free - `server/discover` for servers that no longer answer `initialize`. The tool surface is - validated against the official MCP conformance suite in CI. Also exposes a REST API as - MCP tools from its OpenAPI description. +- **MCP gateway** — front registered upstream MCP servers at `/mcp` with gateway-held + credentials, per-server tool namespaces, and per-caller access. It serves every + Streamable HTTP revision from `2025-03-26` through stateless `2026-07-28` without + downstream sessions. Upstreams use `initialize` by default or `server/discover` with + `protocol_version: "2026-07-28"`. CI runs the official MCP suite's applicable tools-only + protocol scenarios. Also exposes a REST API as MCP tools from its OpenAPI description. - **A2A agent gateway** — front A2A (Agent-to-Agent) agents at `/a2a/:agent`, serving each agent's card with URLs rewritten to the gateway, over JSON-RPC 2.0. - **Inbound authentication** — caller API keys (SHA-256 hashed, model allowlists, expiry,