Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP revision compatibilityMCP 2026-07-28

Implement or negotiate the exact dated MCP revision.

Terminology basis: MCP 2026-07-28. MCP 2026-07-28

MCP revision compatibility: 0 supported, 1 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP revision compatibility?

Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported0
  • Partial1
  • Unsupported0
  • Unknown30
  • Not applicable0

Web

9 products

Desktop

13 products

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Implement or negotiate the exact dated MCP revision.

This row remains unknown for a product until exact, dated evidence covers this capability rather than MCP generally.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Copilot Chatdesktop · current
Partial
Target
VS Code docs and source commit a39698f7 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • protocol-revisioncurrent documentation says VS Code implements the full MCP specification, but the inspected source declares LATEST_PROTOCOL_VERSION as 2025-11-25 rather than 2026-07-28
Evidence
  1. 1. Microsoft documentation broadly claims full MCP support, while the pinned VS Code source still declares 2025-11-25 as its latest protocol version.