7IT Solutions
7MapsOverviewLive chartStateReliableMethodologyVerifyFor agentsFor ownersNews

MCP server cards may not live at a fixed address after all. A catalog would point to them.

By Lior AharonovFounder, 7IT Solutions ·

What happened

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.

Why it matters

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.

What to do

Nothing to do yet; watch for where SEP-2127 settles the card before you publish one at a fixed address.

My take

Lior Aharonov
Founder, 7IT Solutions

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.

Sources

SEP-2127: MCP Server Cards, HTTP Server Discovery (GitHub)github.com
SEP-1913: Trust and Sensitivity Annotations (GitHub)github.com
specificationdiscoverytrust

Researched with AI tools; every fact is checked against the linked sources.

7Maps news

Every 7Maps day is signed and chained to the day before.Verify in your browser