MCP server cards may not live at a fixed address after all. A catalog would point to them.
By Lior AharonovFounder, 7IT Solutions ·
In SEP-2127 (MCP Server Cards, metadata a client reads before it connects), a 24 September comment said the card is not at a generic well-known address and needs an AI Catalog to point to it. SEP-1913 (trust and sensitivity annotations) is being split into small extensions in an experimental repository, with an optional evidenceRef field that carries a digest, a canonicalization and a schema; both proposals are still open.
Publish a card today at a path you picked yourself, and it may sit where no client ever looks. And evidenceRef means a claim about a server can be checked by digest instead of taken on trust, which is how it should be.
Nothing to do yet; watch for where SEP-2127 settles the card before you publish one at a fixed address.
The rules for who gets found are being written right now in a GitHub thread. I'd rather read it this week than learn the result later.
Lior Aharonov · my takeSources
Researched with AI tools; every fact is checked against the linked sources.