Agentic AI Foundation · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Official MCP Registry API

4 actions 4 updates servers extends ../openapi/_original/agentic-ai-foundation-mcp-registry-openapi.yaml
Derived by API Evangelist Built from the contracts Agentic AI Foundation publishes. Agentic AI Foundation did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

serverssecuritySchemescontactx-governancex-api-evangelist-note

Targets 4

$
$.components
$.info
$.paths['/v0/servers']

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Official MCP Registry API
  version: 1.0.0
extends: ../openapi/_original/agentic-ai-foundation-mcp-registry-openapi.yaml
x-provenance:
  generated: '2026-08-30'
  method: derived
  source: openapi/agentic-ai-foundation-mcp-registry-openapi.yaml + live probes of registry.modelcontextprotocol.io
  note: >-
    The upstream specification at https://registry.modelcontextprotocol.io/openapi.yaml is stored verbatim
    and never mutated. Every correction below is expressed as an overlay action so the original stays
    byte-identical to what the provider serves.
actions:
  - target: $
    description: >-
      The published document declares no servers[] block at all, so a generated client has no base URL.
      The live host that serves this document is the base URL.
    update:
      servers:
        - url: https://registry.modelcontextprotocol.io
          description: Official MCP Registry, production (observed serving this document, HTTP 200, 2026-08-30)
  - target: $.components
    description: >-
      Eight operations declare security [{bearer: []}] but components.securitySchemes is absent from the
      document, so the scheme name resolves to nothing. Declare it as the HTTP bearer JWT the registry's
      /auth/* token-exchange endpoints actually issue.
    update:
      securitySchemes:
        bearer:
          type: http
          scheme: bearer
          bearerFormat: JWT
          description: >-
            Registry JWT obtained from one of the /v0/auth/* or /v0.1/auth/* token-exchange endpoints
            (GitHub OAuth access token, GitHub OIDC token, generic OIDC ID token, DNS signature, or HTTP
            signature).
  - target: $.info
    description: Add contact and licence metadata the published info block omits.
    update:
      contact:
        name: Model Context Protocol registry maintainers
        url: https://github.com/modelcontextprotocol/registry/issues
      x-governance:
        hosted-by: Agentic AI Foundation (Linux Foundation)
        project: Model Context Protocol
  - target: $.paths['/v0/servers']
    description: >-
      The /v0 path family duplicates the /v0.1 family operation-for-operation. Mark the older prefix so
      consumers can tell which of the two identical surfaces is current.
    update:
      x-api-evangelist-note: >-
        Duplicate of /v0.1/servers. Both prefixes are live; /v0.1 is the newer of the two version
        families published in the same document. The provider's own documentation is the authority on
        which is preferred — this overlay makes no deprecation claim.

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/agentic-ai-foundation-mcp-registry-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.