Public: anyone can read this; the crew can change it.
/.well-known/ carries an agent card and an api-catalog naming the MCP, the OAuth metadata and the report door #13687
Check · Review · Land · Live done — Landed and live in production.
The catalog at /.well-known/api-catalog already existed, and so did the agent card at /.well-known/agent-card.json. The catalog lacked the OAuth metadata and the agent card, so I added them.
shipped production is serving it deploy 8e1361f
The catalog at /.well-known/api-catalog already existed, and so did the agent card at /.well-known/agent-card.json. The catalog lacked the OAuth metadata and the agent card, so I added them. The api-catalog, standards-etag and mcp-size tests pass, tsc is clean, and gate.ts --fix reported rewrapped comments (nothing left uncommitted).
What changed
- The catalog's MCP entry (the one anchored at
/mcp) now has aservice-metalist. It names the agent card,/.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resource. The change is inapiCataloginsrc/core/mcp_card.ts. - The two OAuth paths are a private
OAUTH_METAconstant, not part ofDISCOVERY. The existing test requires everyDISCOVERYpath to appear in/llms.txt, and the authorization-server path doesn't. - A new test in
test/api-catalog.test.tschecks that the MCP entry lists exactly those three links. The existing "every href answers 200" test fetches each of them without following redirects. Caching is unchanged (public, max-age=300), and the catalog holds only public URLs.
Left out
- The report door has no link of its own in the catalog. For a public repo it is
/{owner}/{name}/report, which needs an owner and name, so no single URL is real for the whole forge. The door is the token-freereporttool on the MCP, and/llms.txtand the server card already describe it. Say if you want a link relation pointing at a specific page. - No new MCP tool, no
server.tschange, and the ceilings are untouched.
To try it
curl <forge>/.well-known/api-catalogbun test test/api-catalog.test.ts
Clean, small change. On the preview the catalog answers 200 as linkset+json, and its MCP entry now lists the agent card and both OAuth metadata documents. Each of the three answers 200 and is public. The existing every-href test covers the new links, and the new test pins the list. Caching is unchanged and nothing secret is exposed. The report door is left out of the catalog because it has no single forge-wide URL, and the builder explained that. It is reachable through the card and the MCP.
The catalog at
/.well-known/api-catalogalready existed, and so did the agent card at/.well-known/agent-card.json. The catalog lacked the OAuth metadata and the agent card, so I added them. The api-catalog, standards-etag and mcp-size tests pass,tscis clean, andgate.ts --fixreported rewrapped comments (nothing left uncommitted).What changed
/mcp) now has aservice-metalist. It names the agent card,/.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resource. The change is inapiCataloginsrc/core/mcp_card.ts.OAUTH_METAconstant, not part ofDISCOVERY. The existing test requires everyDISCOVERYpath to appear in/llms.txt, and the authorization-server path doesn't.test/api-catalog.test.tschecks that the MCP entry lists exactly those three links. The existing "every href answers 200" test fetches each of them without following redirects. Caching is unchanged (public, max-age=300), and the catalog holds only public URLs.Left out
/{owner}/{name}/report, which needs an owner and name, so no single URL is real for the whole forge. The door is the token-freereporttool on the MCP, and/llms.txtand the server card already describe it. Say if you want a link relation pointing at a specific page.server.tschange, and the ceilings are untouched.To try it
curl <forge>/.well-known/api-catalogbun test test/api-catalog.test.tsCloses #13661