Vercel MCP OAuth metadata
urn:air:vercel.com:metadata:mcp-oauth
OAuth protected-resource metadata for connecting clients to Vercel MCP.
application/json
artifact →
AI Catalog manifest · Vercel
Vercel
Vercel serves an AI Catalog
manifest at /.well-known/ai-catalog.json on vercel.com, declaring
4 agentic resources
that a discovery service can index without asking anyone’s permission.
Structural grade · AI Catalog 1.0
Near-Conformant
Correctly shaped — every hard check passes — but optional affordances are missing.
ARD conformance-test v0.9.1 (ards-project/ard-spec)
PASS
Run against this exact body with the project’s own
conformance CLI.
Discovery path
predecessor
Answered only at
/.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.
Declared spec version
1.0
The
specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.
Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
entry-no-representativeQuerieshost-identifier-not-did-web
What this manifest advertises
Vercel REST API
urn:air:vercel.com:api:rest
The OpenAPI 3.0 description for the public Vercel REST API.
application/json
artifact →
Vercel agent resources
urn:air:vercel.com:docs:agent-resources
Machine-readable documentation for Vercel agent resources, including MCP, skills, and Markdown access.
text/markdown
artifact →
Vercel documentation graph
urn:air:vercel.com:docs:graph
Cross-site documentation graph with page links, prerequisites, semantic neighbors, and related pages.
application/json
artifact →
How it is served
The publishing guide asks for three things at the transport layer, because a crawler is the
consumer that matters and a crawler is a browser-shaped client.
- HTTPS only — yes (HTTP 200)
Content-Type: application/json— no — servesapplication/ai-catalog+jsonAccess-Control-Allow-Origin: *— yes
Evidence. Fetched
https://vercel.com/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Vercel repository
as ai-catalog/vercel-ai-catalog.json. Nothing on this page is derived
or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not
exist, which makes it — like an
A2A Agent Card — one of the few agent artifacts that cannot be
produced on a provider’s behalf. Grades are recomputed on every build; the specification is a
v0.9 draft and
these verdicts will move when it does.
Work with this as data
Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.