Agent endpoint discovery (MCP Server Card + DNS-AID)

[kaankacar]

Two agent-discovery checks from the isitagentready scan ( MCP Server Card (SEP-1649) and DNS-AID ) both need an endpoint we don't have: an official docs MCP server. (PR #2440 already handles the server-independent bits: api-catalog, agent-skills.)

We shouldn't publish a card or DNS record pointing at a nonexistent server, agents would just try to connect and fail.

The real decision

Do we want to run an official Stellar docs MCP server? No official one exists today (stellar-dev-skill / stellar-build is adjacent, but not an MCP server). Everything below is blocked on this.

If yes → two channels, same target

1. MCP Server Card : static file static/.well-known/mcp/server-card.json (serverInfo, transport endpoint, capabilities). Repo task, like the api-catalog. Schema still draft (modelcontextprotocol#2127).
2. DNS-AID _mcp record : SVCB record _mcp._agents.developers.stellar.org → the endpoint. Cloudflare/infra task, not repo. DNSSEC (currently off) optional, can follow later.

Refs

• MCP card: SEP-2127: MCP Server Cards - HTTP Server Discovery  modelcontextprotocol/modelcontextprotocol#2127
• DNS-AID: https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/ · SVCB: https://www.rfc-editor.org/rfc/rfc9460

[kaankacar]

Update, 2026-09-08.

The blocker is gone. Stellar Raven is live at https://raven.stellar.org/mcp (streamable HTTP, OAuth). The docs already point to it (#2588).

I ran the isitagentready scan today. The site is Level 4. Two discovery checks fail: MCP Server Card and DNS-AID.

MCP Server Card: doing it. A PR follows. It adds:

• static/.well-known/mcp/server-card.json. It points to Raven.
• static/.well-known/ai-catalog.json. It lists the card, the agent-skills index, the api-catalog, and llms.txt. The current SEP-2127 draft recommends this discovery path. It also passes the scanner's ARD check.

The scanner accepts a card that points to an OAuth-protected server on another host. developers.cloudflare.com passes this way.

DNS-AID: not needed at this point.

• The scanner does not require it for any level. Level 5 needs auth.md, an MCP card, and an A2A card.
• No domain I tested publishes the records. developers.cloudflare.com and isitagentready.com fail the same check.
• No MCP client does DNS-AID lookups today.
• The draft (rev 02) is an individual submission. No working group has adopted it. It expires 2026-11-28.
• The record would live in the stellar.org Cloudflare zone. That is an ops change, not a repo change.

We can revisit DNS-AID when a working group adopts the draft or a client consumes the records.

[kaankacar]

🤖 Automated triage bot, acting for @kaankacar.

Standing down. @kaankacar is assigned, and #2832 is open for the MCP server card.

One note: #2832 says "Closes #2555". A merge closes this issue, so the deferred DNS-AID work needs a new issue.