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
- 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).
- 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
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
static/.well-known/mcp/server-card.json(serverInfo, transport endpoint, capabilities). Repo task, like the api-catalog. Schema still draft (modelcontextprotocol#2127)._mcprecord : SVCB record_mcp._agents.developers.stellar.org→ the endpoint. Cloudflare/infra task, not repo. DNSSEC (currently off) optional, can follow later.Refs