Specification feature · interfaces
MCP Registry metadataMCP 2026-07-28
Discover MCP servers and metadata through the official registry model.
Terminology basis: MCP 2026-07-28. MCP 2026-07-28
MCP Registry metadata: 1 supported, 0 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.
Current evidence by product
Can my agent use MCP Registry metadata?
Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.
Web
9 productsDesktop
13 productsCLI
9 productsDefinition and scope
What this capability means
Discover MCP servers and metadata through the official registry model.
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.
- Target
- VS Code documentation dated 2026-08-26 · dated-documentation
- Environment
- enterprise-managed
- Observed
- 2026-08-28
- policyan administrator configures the registry with McpGalleryServiceUrl; registry-only policy can restrict installs to its catalog
- Microsoft VS Code — Configure MCP server access and custom registriesdocumented · reviewed 2026-08-28
- 1. VS Code can browse and install MCP server metadata from an administrator-configured registry and can restrict access to registry-listed servers.
No sourced issues are attached to this row.
- Model Context Protocol specification spec
- Microsoft VS Code — Configure MCP server access and custom registries documented · Microsoft · reviewed 2026-08-28
Found a wrong or incomplete result?
Name the exact product, describe what happened, add the date, and link public evidence when available. A community report starts a review. It does not change the support state by itself.