How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Official MCP Registry API

The Official MCP Registry is the community registry service for Model Context Protocol servers, run by the MCP project. Its REST API publishes a full OpenAPI 3.1.0 contract with 32 operations across two live version prefixes (/v0.1 and /v0). Reads are anonymous — list, search and fetch server records with cursor pagination and an updated_since incremental-sync filter; writes require a Registry JWT minted by proving namespace ownership through GitHub OAuth, GitHub or generic OIDC, a DNS signature, or an HTTP signature. Errors are RFC 9457 problem details.

Official MCP Registry API is one of 6 APIs that Agentic AI Foundation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include MCP, Registry, Server Discovery, Open Standard, and REST API. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a GitHub repository, and authentication docs.

This API exposes 32 operations across 30 paths, organized into 7 resource areas, and defines 28 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against the base URL https://registry.modelcontextprotocol.io.

32 operations 30 paths 28 schemas 12 GET4 PATCH14 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://registry.modelcontextprotocol.io
Resource Areas
7

Paths & Operations 32

Across 30 paths, the API surfaces 32 operations — 12 GET, 4 PATCH, 14 POST, 2 PUT. They span 7 resource areas: auth, health, ping, publish, servers, validate, version. Each is listed below with its method, path, parameters, and response codes.

auth 10

Authentication operations for obtaining tokens to publish servers

POST
/v0.1/auth/dns
Exchange DNS signature for Registry JWT
exchange-dns-token-v0.1 body → 200default
POST
/v0.1/auth/github-at
Exchange GitHub OAuth access token for Registry JWT
exchange-github-token-v0.1 body → 200default
POST
/v0.1/auth/github-oidc
Exchange GitHub OIDC token for Registry JWT
exchange-github-oidc-token-v0.1 body → 200default
POST
/v0.1/auth/http
Exchange HTTP signature for Registry JWT
exchange-http-token-v0.1 body → 200default
POST
/v0.1/auth/oidc
Exchange OIDC ID token for Registry JWT
exchange-oidc-token-v0.1 body → 200default
POST
/v0/auth/dns
Exchange DNS signature for Registry JWT
exchange-dns-token-v0 body → 200default
POST
/v0/auth/github-at
Exchange GitHub OAuth access token for Registry JWT
exchange-github-token-v0 body → 200default
POST
/v0/auth/github-oidc
Exchange GitHub OIDC token for Registry JWT
exchange-github-oidc-token-v0 body → 200default
POST
/v0/auth/http
Exchange HTTP signature for Registry JWT
exchange-http-token-v0 body → 200default
POST
/v0/auth/oidc
Exchange OIDC ID token for Registry JWT
exchange-oidc-token-v0 body → 200default
health 2

Health check endpoint for monitoring service availability

GET
/v0.1/health
Health check
get-health-v0.1 → 200default
GET
/v0/health
Health check
get-health-v0 → 200default
ping 2

Simple ping endpoint for testing connectivity

GET
/v0.1/ping
Ping
ping-v0.1 → 200default
GET
/v0/ping
Ping
ping-v0 → 200default
publish 2

Operations for publishing MCP servers to the registry

POST
/v0.1/publish
Publish MCP server
publish-server-v0.1 1 param body → 200default
POST
/v0/publish
Publish MCP server
publish-server-v0 1 param body → 200default
servers 12

Operations for discovering and retrieving MCP servers

GET
/v0.1/servers
List MCP servers
list-servers-v0.1 6 params → 200default
PATCH
/v0.1/servers/{serverName}/status
Update status for all versions of an MCP server
update-server-all-versions-status-v0.1 2 params body → 200default
GET
/v0.1/servers/{serverName}/versions
Get all versions of an MCP server
get-server-versions-v0.1 2 params → 200default
GET
/v0.1/servers/{serverName}/versions/{version}
Get specific MCP server version
get-server-version-v0.1 3 params → 200default
PUT
/v0.1/servers/{serverName}/versions/{version}
Edit MCP server
edit-server-v0.1 3 params body → 200default
PATCH
/v0.1/servers/{serverName}/versions/{version}/status
Update MCP server status
update-server-status-v0.1 3 params body → 200default
GET
/v0/servers
List MCP servers
list-servers-v0 6 params → 200default
PATCH
/v0/servers/{serverName}/status
Update status for all versions of an MCP server
update-server-all-versions-status-v0 2 params body → 200default
GET
/v0/servers/{serverName}/versions
Get all versions of an MCP server
get-server-versions-v0 2 params → 200default
GET
/v0/servers/{serverName}/versions/{version}
Get specific MCP server version
get-server-version-v0 3 params → 200default
PUT
/v0/servers/{serverName}/versions/{version}
Edit MCP server
edit-server-v0 3 params body → 200default
PATCH
/v0/servers/{serverName}/versions/{version}/status
Update MCP server status
update-server-status-v0 3 params body → 200default
validate 2
POST
/v0.1/validate
Validate MCP server JSON
validate-server-v0.1 body → 200default
POST
/v0/validate
Validate MCP server JSON
validate-server-v0 body → 200default
version 2

Version information endpoint for retrieving build and version details

GET
/v0.1/version
Get version information
get-version-v0.1 → 200default
GET
/v0/version
Get version information
get-version-v0 → 200default

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Argument (13 properties), ServerJSON (11 properties), KeyValueInput (10 properties), Package (10 properties). Each schema is shown below with its type and property counts.

Argument
object
13 properties 1 required
ErrorDetail
object
3 properties
ErrorModel
object
6 properties
GitHubOIDCTokenExchangeInputBody
object
1 property 1 required
GitHubTokenExchangeInputBody
object
1 property 1 required
HealthBody
object
2 properties 1 required
Icon
object
4 properties 1 required
Input
object
8 properties
KeyValueInput
object
10 properties 1 required
Metadata
object
2 properties 1 required
OIDCTokenExchangeInputBody
object
1 property 1 required
Package
object
10 properties 3 required
PingBody
object
1 property 1 required
RegistryExtensions
object
6 properties 4 required
Repository
object
4 properties
ResponseMeta
object
1 property
ServerJSON
object
11 properties 4 required
ServerListResponse
object
2 properties 2 required
ServerMeta
object
1 property
ServerResponse
object
2 properties 2 required
SignatureTokenExchangeInput
object
3 properties 3 required
TokenResponse
object
2 properties 2 required
Transport
object
4 properties 1 required
UpdateAllVersionsStatusResponse
object
2 properties 2 required
UpdateServerStatusBody
object
2 properties 1 required
ValidationIssue
object
5 properties 5 required
ValidationResult
object
2 properties 2 required
VersionBody
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

agentic-ai-foundation-mcp-registry-openapi.yaml Raw ↑

Other APIs Agentic AI Foundation publishes across the network.

Model Context Protocol (MCP)
Goose AI Agent
AGENTS.md
Agent2Agent (A2A)
agentgateway
Where this information came from

This is an independent, third-party profile of Official MCP Registry API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.