--- a/base/index.html
+++ b/head/index.html
@@ -200,7 +200,7 @@
     {
       &quot;identifier&quot;: &quot;urn:air:example.com:mcp:weather&quot;,
       &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-      &quot;url&quot;: &quot;https://api.example.com/.well-known/mcp/server-card.json&quot;
+      &quot;url&quot;: &quot;https://api.example.com/mcp/server-card&quot;
     },
     {
       &quot;identifier&quot;: &quot;urn:air:example.com:a2a:research&quot;,
@@ -1387,7 +1387,7 @@
       &quot;identifier&quot;: &quot;urn:air:acme.com:server:finance-mcp&quot;,
       &quot;version&quot;: &quot;1.4.0&quot;,
       &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-      &quot;url&quot;: &quot;https://api.acme-corp.com/.well-known/mcp/server-card.json&quot;,
+      &quot;url&quot;: &quot;https://api.acme-corp.com/mcp/server-card&quot;,
       &quot;description&quot;: &quot;MCP server with finance tools.&quot;,
       &quot;tags&quot;: [&quot;finance&quot;, &quot;mcp&quot;],
       &quot;updatedAt&quot;: &quot;2026-03-15T10:00:00Z&quot;
@@ -1409,7 +1409,7 @@
           {
             &quot;identifier&quot;: &quot;urn:air:acme.com:server:finance-mcp&quot;,
             &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-            &quot;url&quot;: &quot;https://api.acme-corp.com/.well-known/mcp/server-card.json&quot;
+            &quot;url&quot;: &quot;https://api.acme-corp.com/mcp/server-card&quot;
           },
           {
             &quot;identifier&quot;: &quot;urn:air:acme.com:data:market-2026q1&quot;,
@@ -1512,7 +1512,7 @@
       {
         &quot;identifier&quot;: &quot;urn:air:acme.com:agent:finance:mcp&quot;,
         &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-        &quot;url&quot;: &quot;https://api.acme-corp.com/.well-known/mcp/server-card.json&quot;
+        &quot;url&quot;: &quot;https://api.acme-corp.com/mcp/server-card&quot;
       },
       {
         &quot;identifier&quot;: &quot;urn:air:acme.com:agent:finance:a2a&quot;,
@@ -1800,264 +1800,31 @@
 while infrastructure-oriented deployments leverage OCI distribution.</p>
 </section>
 </section>
-<section class="appendix" id="mapping-to-mcp-registry-server-json">
-<h1>Mapping to MCP Registry server.json</h1>
-<p>This appendix describes how the MCP Registry <code>server.json</code> format
-(see <a href="https://github.com/modelcontextprotocol/registry">modelcontextprotocol/registry</a>)
-relates to AI Catalog, enabling MCP servers to be discovered alongside
-other AI artifacts through a unified catalog.</p>
-<blockquote>
-<p><strong>Note:</strong> The MCP ecosystem defines two distinct metadata documents
-for servers. The <strong>Registry <code>server.json</code></strong> is an installable package
-descriptor (package coordinates, transports, environment variables).
-The <strong>MCP Server Card</strong> (<a href="#relationship-to-mcp-server-cards-sep-1649">SEP-1649</a>)
-is a runtime discovery document at <code>/.well-known/mcp/server-card.json</code>
-describing capabilities, tools, and authentication. An AI Catalog
-entry can reference either artifact depending on the use case — use
-<code>server.json</code> for installable packages and Server Cards for
-connectable HTTP endpoints.</p>
-</blockquote>
+<section class="appendix" id="mapping-to-mcp-servers">
+<h1>Mapping to MCP Servers</h1>
+<p>This appendix describes how <strong>remote (HTTP-connectable) MCP servers</strong>
+map to AI Catalog, enabling them to be discovered alongside other AI
+artifacts through a unified catalog. The documented, supported path is
+to reference each server's <strong>MCP Server Card</strong>
+(<a href="https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127">SEP-2127</a>)
+as the artifact content of a Catalog Entry.</p>
+<p>A Server Card is a static discovery document for a single HTTP-based MCP
+server (its identity and connection details). It is distinct from the MCP
+Registry's <code>server.json</code>, an installable-package descriptor — a separate
+artifact type that this appendix does not address.</p>
 <section id="overview">
 <h2>Overview</h2>
-<p>The MCP Registry defines a <code>server.json</code> format for describing MCP
-servers. Each <code>server.json</code> document captures everything needed to
-install, configure, and connect to a single MCP server: package
-coordinates (npm, PyPI, NuGet, OCI), remote endpoints (streamable-http,
-SSE), transport configuration, environment variables, and CLI arguments.</p>
-<p>In AI Catalog terms, a <code>server.json</code> document is the <strong>artifact
-content</strong> — the native metadata that a Catalog Entry references. The
-AI Catalog does not duplicate or redefine <code>server.json</code> fields.
-Instead, it provides the discovery and trust layer that <code>server.json</code>
-does not address.</p>
-</section>
-<section id="conceptual-mapping-2">
-<h2>Conceptual Mapping</h2>
-<table>
-<thead>
-<tr>
-<th style="text-align: left;">MCP <code>server.json</code></th>
-<th style="text-align: left;">AI Catalog Equivalent</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td style="text-align: left;"><code>server.json</code> document (whole file)</td>
-<td style="text-align: left;">Artifact content via entry <code>url</code> or <code>data</code></td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>name</code> (reverse-DNS identifier)</td>
-<td style="text-align: left;">Entry <code>identifier</code> (mapped to URI form)</td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>title</code></td>
-<td style="text-align: left;">Stays in the artifact (<code>server.json</code> carries its own <code>title</code>); entry <code>displayName</code> is omitted unless the artifact lacks a name</td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>description</code></td>
-<td style="text-align: left;">Entry <code>description</code></td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>version</code></td>
-<td style="text-align: left;">Entry <code>version</code></td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>repository</code></td>
-<td style="text-align: left;">Entry <code>metadata.repository</code></td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>packages[]</code> (npm, pypi, nuget, oci)</td>
-<td style="text-align: left;">Inside the artifact — not surfaced in catalog</td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>remotes[]</code> (streamable-http, sse)</td>
-<td style="text-align: left;">Inside the artifact — not surfaced in catalog</td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>environmentVariables[]</code></td>
-<td style="text-align: left;">Inside the artifact — not surfaced in catalog</td>
-</tr>
-<tr>
-<td style="text-align: left;"><code>_meta</code></td>
-<td style="text-align: left;">Entry <code>metadata</code> for catalog-level hints; otherwise stays in artifact</td>
-</tr>
-<tr>
-<td style="text-align: left;"><em>(not in server.json)</em></td>
-<td style="text-align: left;">Entry <code>publisher</code></td>
-</tr>
-<tr>
-<td style="text-align: left;"><em>(not in server.json)</em></td>
-<td style="text-align: left;">Entry <code>trustManifest</code> (identity, attestations, provenance)</td>
-</tr>
-<tr>
-<td style="text-align: left;"><em>(not in server.json)</em></td>
-<td style="text-align: left;">Entry <code>tags</code> for cross-artifact discovery</td>
-</tr>
-<tr>
-<td style="text-align: left;">MCP Registry (centralized service)</td>
-<td style="text-align: left;">AI Catalog (decentralized, any URL)</td>
-</tr>
-</tbody>
-</table>
-</section>
-<section id="separation-of-concerns">
-<h2>Separation of Concerns</h2>
-<p>The <code>server.json</code> format and AI Catalog address different concerns:</p>
-<dl>
-<dt>server.json (Operational)</dt>
-<dd>How do I install this server? What packages, transports, arguments,
-  and environment variables does it need?</dd>
-<dt>AI Catalog (Discovery + Trust)</dt>
-<dd>What servers exist? Who published them? Can I trust them? Where is
-  their metadata?</dd>
-</dl>
-<p>This separation means the AI Catalog entry is thin — it points at the
-<code>server.json</code> and adds only what <code>server.json</code> lacks: publisher
-identity, trust verification, and cross-ecosystem discoverability.</p>
-</section>
-<section id="mcp-server-as-catalog-entry">
-<h2>MCP Server as Catalog Entry</h2>
-<p>An MCP server listed in the Registry maps to a Catalog Entry whose
-<code>url</code> points to the <code>server.json</code> document and whose <code>type</code>
-reflects the Registry format:</p>
-<pre><code class="language-json">{
-  &quot;identifier&quot;: &quot;urn:air:anonymous.modelcontextprotocol.io:mcp:brave-search&quot;,
-  &quot;version&quot;: &quot;1.0.2&quot;,
-  &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-  &quot;url&quot;: &quot;https://registry.modelcontextprotocol.io/servers/brave-search/server.json&quot;,
-  &quot;description&quot;: &quot;MCP server for Brave Search API integration&quot;,
-  &quot;tags&quot;: [&quot;search&quot;, &quot;brave&quot;, &quot;web&quot;],
-  &quot;publisher&quot;: {
-    &quot;identifier&quot;: &quot;did:web:modelcontextprotocol.io&quot;,
-    &quot;displayName&quot;: &quot;Model Context Protocol&quot;
-  },
-  &quot;trustManifest&quot;: {
-    &quot;identity&quot;: &quot;did:web:anonymous.modelcontextprotocol.io:mcp:brave-search&quot;,
-    &quot;attestations&quot;: [
-      {
-        &quot;type&quot;: &quot;publisher-identity&quot;,
-        &quot;uri&quot;: &quot;https://registry.modelcontextprotocol.io/certs/publisher.jwt&quot;,
-        &quot;description&quot;: &quot;Verifies did:web:modelcontextprotocol.io as publisher&quot;
-      }
-    ],
-    &quot;provenance&quot;: [
-      {
-        &quot;relation&quot;: &quot;publishedFrom&quot;,
-        &quot;sourceId&quot;: &quot;https://github.com/modelcontextprotocol/servers&quot;,
-        &quot;registryUri&quot;: &quot;https://registry.npmjs.org&quot;
-      }
-    ]
-  },
-  &quot;metadata&quot;: {
-    &quot;repository&quot;: &quot;https://github.com/modelcontextprotocol/servers&quot;
-  },
-  &quot;updatedAt&quot;: &quot;2026-03-15T10:00:00Z&quot;
-}
-</code></pre>
-<p>The <code>url</code> points to the complete <code>server.json</code>. A client fetches the
-catalog entry for discovery and trust evaluation, then retrieves the
-<code>server.json</code> for operational details (packages, transports, env vars).</p>
-<blockquote>
-<p><strong>Note:</strong> This example uses <code>application/json</code> because the MCP
-Registry has not registered a dedicated media type for <code>server.json</code>.
-When referencing an MCP Server Card (SEP-1649) instead, use
-<code>application/mcp-server-card+json</code> — see
-<a href="#relationship-to-mcp-server-cards-sep-1649">Relationship to MCP Server Cards</a>.</p>
-</blockquote>
-</section>
-<section id="mcp-registry-as-ai-catalog">
-<h2>MCP Registry as AI Catalog</h2>
-<p>The MCP Registry — a centralized index of MCP servers — can be
-represented as an AI Catalog. This enables clients that understand
-<code>application/ai-catalog+json</code> to discover MCP servers alongside A2A
-agents, skills, and other artifacts:</p>
-<pre><code class="language-json">{
-  &quot;specVersion&quot;: &quot;1.0&quot;,
-  &quot;host&quot;: {
-    &quot;displayName&quot;: &quot;MCP Server Registry&quot;,
-    &quot;identifier&quot;: &quot;did:web:modelcontextprotocol.io&quot;,
-    &quot;documentationUrl&quot;: &quot;https://modelcontextprotocol.io/docs&quot;
-  },
-  &quot;entries&quot;: [
-    {
-      &quot;identifier&quot;: &quot;urn:air:anonymous.modelcontextprotocol.io:mcp:brave-search&quot;,
-      &quot;version&quot;: &quot;1.0.2&quot;,
-      &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-      &quot;url&quot;: &quot;https://registry.modelcontextprotocol.io/servers/brave-search/server.json&quot;,
-      &quot;description&quot;: &quot;MCP server for Brave Search API integration&quot;,
-      &quot;tags&quot;: [&quot;search&quot;, &quot;brave&quot;]
-    },
-    {
-      &quot;identifier&quot;: &quot;urn:air:modelcontextprotocol.github.io:mcp:filesystem&quot;,
-      &quot;version&quot;: &quot;1.0.2&quot;,
-      &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-      &quot;url&quot;: &quot;https://registry.modelcontextprotocol.io/servers/filesystem/server.json&quot;,
-      &quot;description&quot;: &quot;MCP server for filesystem operations&quot;,
-      &quot;tags&quot;: [&quot;filesystem&quot;, &quot;files&quot;]
-    },
-    {
-      &quot;identifier&quot;: &quot;urn:air:example.github.io:mcp:weather-mcp&quot;,
-      &quot;version&quot;: &quot;0.5.0&quot;,
-      &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-      &quot;url&quot;: &quot;https://registry.modelcontextprotocol.io/servers/weather/server.json&quot;,
-      &quot;description&quot;: &quot;Python MCP server for weather data access&quot;,
-      &quot;tags&quot;: [&quot;weather&quot;, &quot;python&quot;],
-      &quot;publisher&quot;: {
-        &quot;identifier&quot;: &quot;did:web:example.github.io&quot;,
-        &quot;displayName&quot;: &quot;Example Corp&quot;
-      }
-    }
-  ]
-}
-</code></pre>
-</section>
-<section id="decentralized-discovery">
-<h2>Decentralized Discovery</h2>
-<p>The MCP Registry is a centralized service. AI Catalog enables
-decentralized discovery: any domain can publish its MCP servers at
-<code>/.well-known/ai-catalog.json</code> without registering with a central
-authority.</p>
-<p>A vendor hosting its own MCP servers can publish:</p>
-<pre><code>https://api.acme-corp.com/.well-known/ai-catalog.json
-</code></pre>
-<p>Clients and crawlers discover the catalog via the well-known URL,
-find entries by <code>type</code>, and fetch the referenced artifacts for
-operational details — whether those are MCP Server Cards, Registry
-<code>server.json</code> documents, or other AI artifact formats.</p>
-<p>The centralized MCP Registry and decentralized AI Catalogs are
-complementary. The registry can serve an AI Catalog as its response
-format, while individual domains publish their own catalogs for
-direct discovery.</p>
-</section>
-<section id="what-ai-catalog-adds-to-server-json">
-<h2>What AI Catalog Adds to server.json</h2>
-<p>The <code>server.json</code> format has no trust or identity layer. AI Catalog
-fills this gap:</p>
-<ol>
-<li><strong>Publisher identity</strong>: Verifiable publisher with DID or domain
-   anchor, absent from <code>server.json</code>.</li>
-<li><strong>Trust verification</strong>: Attestations (SOC2, HIPAA, publisher
-   identity proofs) via the Trust Manifest.</li>
-<li><strong>Provenance</strong>: Links to source repositories, registries, and
-   build artifacts with cryptographic digests.</li>
-<li><strong>Signing</strong>: Detached JWS signature on the Trust Manifest for
-   integrity verification.</li>
-<li><strong>Cross-ecosystem discovery</strong>: MCP servers become discoverable
-   alongside A2A agents, plugins, and datasets through a single
-   catalog format.</li>
-<li><strong>Composability</strong>: MCP servers can be packaged with related
-   artifacts (A2A agents, datasets) in nested catalogs.</li>
-</ol>
-</section>
-<section id="relationship-to-mcp-server-cards-sep-1649">
-<h2>Relationship to MCP Server Cards (SEP-1649)</h2>
-<p>MCP Server Cards
-(<a href="https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1649">SEP-1649</a>)
-define a static discovery document for individual HTTP-based MCP
-servers at <code>/.well-known/mcp/server-card.json</code>. A Server Card mirrors
-the MCP initialization handshake response: it carries the server's
-name, version, transport configuration, capabilities, authentication
-requirements, and optionally the full list of tools, resources, and
-prompts.</p>
+<p>An MCP Server Card is a static discovery document for an individual
+HTTP-based MCP server, describing its identity and how to connect to it.
+A Catalog Entry references the card wherever the server publishes it, as
+in the examples below. See
+<a href="https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127">SEP-2127</a>
+for the Server Card's schema, fields, and hosting conventions.</p>
+<p>In AI Catalog terms, the Server Card is the <strong>artifact content</strong> — the
+native metadata that a Catalog Entry references via its <code>url</code>, declared
+with the known type <code>application/mcp-server-card+json</code>. The AI Catalog
+does not duplicate or redefine Server Card fields; it provides the
+discovery and trust layer that the Server Card does not address.</p>
 <p>AI Catalog and MCP Server Cards address different layers of discovery:</p>
 <dl>
 <dt>MCP Server Card (per-server)</dt>
@@ -2069,12 +1836,70 @@
   trust them? What other artifact types are available alongside MCP
   servers?</dd>
 </dl>
-<p>The two mechanisms layer naturally. An AI Catalog entry for an MCP
-server can reference the Server Card as its artifact content:</p>
+</section>
+<section id="conceptual-mapping-2">
+<h2>Conceptual Mapping</h2>
+<table>
+<thead>
+<tr>
+<th style="text-align: left;">MCP Server Card</th>
+<th style="text-align: left;">AI Catalog Equivalent</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align: left;">Server Card document (whole file)</td>
+<td style="text-align: left;">Artifact content via entry <code>url</code> (type <code>application/mcp-server-card+json</code>) or <code>data</code></td>
+</tr>
+<tr>
+<td style="text-align: left;">Server <code>name</code> (reverse-DNS identifier)</td>
+<td style="text-align: left;">Entry <code>identifier</code> (mapped to the <code>urn:air:{publisher}:{namespace}:{name}</code> URN form — e.g. <code>urn:air:example.com:mcp:finance-server</code>)</td>
+</tr>
+<tr>
+<td style="text-align: left;"><code>title</code></td>
+<td style="text-align: left;">Stays in the Server Card (which carries its own <code>title</code>); entry <code>displayName</code> is omitted unless the artifact lacks a name</td>
+</tr>
+<tr>
+<td style="text-align: left;"><code>description</code></td>
+<td style="text-align: left;">Entry <code>description</code></td>
+</tr>
+<tr>
+<td style="text-align: left;"><code>version</code></td>
+<td style="text-align: left;">Entry <code>version</code></td>
+</tr>
+<tr>
+<td style="text-align: left;">transport / capabilities / tools / resources / auth</td>
+<td style="text-align: left;">Inside the Server Card — not surfaced in the catalog</td>
+</tr>
+<tr>
+<td style="text-align: left;"><code>repository</code></td>
+<td style="text-align: left;">Entry <code>metadata.repository</code></td>
+</tr>
+<tr>
+<td style="text-align: left;"><em>(not in the Server Card)</em></td>
+<td style="text-align: left;">Entry <code>publisher</code></td>
+</tr>
+<tr>
+<td style="text-align: left;"><em>(not in the Server Card)</em></td>
+<td style="text-align: left;">Entry <code>trustManifest</code> (identity, attestations, provenance)</td>
+</tr>
+<tr>
+<td style="text-align: left;"><em>(not in the Server Card)</em></td>
+<td style="text-align: left;">Entry <code>tags</code> for cross-artifact discovery</td>
+</tr>
+</tbody>
+</table>
+</section>
+<section id="mcp-server-as-catalog-entry">
+<h2>MCP Server as Catalog Entry</h2>
+<p>A remote MCP server maps to a Catalog Entry whose <code>url</code> points to the
+server's Server Card and whose <code>type</code> is the known type
+<code>application/mcp-server-card+json</code>:</p>
 <pre><code class="language-json">{
   &quot;identifier&quot;: &quot;urn:air:example.com:mcp:finance-server&quot;,
+  &quot;version&quot;: &quot;1.0.2&quot;,
   &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
-  &quot;url&quot;: &quot;https://api.acme-corp.com/.well-known/mcp/server-card.json&quot;,
+  &quot;url&quot;: &quot;https://api.acme-corp.com/mcp/server-card&quot;,
   &quot;description&quot;: &quot;MCP server for financial data and trading tools&quot;,
   &quot;tags&quot;: [&quot;finance&quot;, &quot;mcp&quot;],
   &quot;publisher&quot;: {
@@ -2097,11 +1922,74 @@
   }
 }
 </code></pre>
+<blockquote>
+<p><strong>Note on <code>type</code>:</strong> The <code>type</code> member is an open-text type identifier
+(<a href="https://github.com/Agent-Card/ai-catalog/blob/main/adr/0014-media-type-to-type.md">ADR 0014</a>);
+any string is accepted, with a recommended set of "known types." The
+known type for an MCP server referenced by its Server Card is
+<code>application/mcp-server-card+json</code>. Note the deliberate naming
+distinction: the MCP Server Card extension uses
+<code>application/mcp-server-card+json</code> (not <code>application/mcp-server+json</code>)
+to avoid colliding with the MCP Registry's <code>server.json</code> concept
+(modelcontextprotocol/experimental-ext-server-card issue #9 / PR #18).</p>
+</blockquote>
+</section>
+<section id="mcp-servers-as-an-ai-catalog">
+<h2>MCP Servers as an AI Catalog</h2>
+<p>A domain that hosts remote MCP servers can publish them as an AI Catalog,
+letting clients that understand <code>application/ai-catalog+json</code> discover
+those servers alongside A2A agents, skills, and other artifacts. Each
+entry points to a server's Server Card:</p>
+<pre><code class="language-json">{
+  &quot;specVersion&quot;: &quot;1.0&quot;,
+  &quot;host&quot;: {
+    &quot;displayName&quot;: &quot;Acme MCP Servers&quot;,
+    &quot;identifier&quot;: &quot;did:web:acme-corp.com&quot;,
+    &quot;documentationUrl&quot;: &quot;https://acme-corp.com/docs&quot;
+  },
+  &quot;entries&quot;: [
+    {
+      &quot;identifier&quot;: &quot;urn:air:acme-corp.com:mcp:finance-server&quot;,
+      &quot;version&quot;: &quot;1.0.2&quot;,
+      &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
+      &quot;url&quot;: &quot;https://api.acme-corp.com/finance/server-card&quot;,
+      &quot;description&quot;: &quot;MCP server for financial data and trading tools&quot;,
+      &quot;tags&quot;: [&quot;finance&quot;, &quot;mcp&quot;]
+    },
+    {
+      &quot;identifier&quot;: &quot;urn:air:acme-corp.com:mcp:docs-search&quot;,
+      &quot;version&quot;: &quot;1.0.2&quot;,
+      &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
+      &quot;url&quot;: &quot;https://api.acme-corp.com/docs-search/server-card&quot;,
+      &quot;description&quot;: &quot;MCP server for searching internal documentation&quot;,
+      &quot;tags&quot;: [&quot;search&quot;, &quot;docs&quot;]
+    },
+    {
+      &quot;identifier&quot;: &quot;urn:air:acme-corp.com:mcp:ci-cd&quot;,
+      &quot;version&quot;: &quot;0.5.0&quot;,
+      &quot;type&quot;: &quot;application/mcp-server-card+json&quot;,
+      &quot;url&quot;: &quot;https://api.acme-corp.com/ci-cd/server-card&quot;,
+      &quot;description&quot;: &quot;MCP server for CI/CD pipeline operations&quot;,
+      &quot;tags&quot;: [&quot;ci&quot;, &quot;cd&quot;, &quot;devops&quot;]
+    }
+  ]
+}
+</code></pre>
+</section>
+<section id="decentralized-discovery">
+<h2>Decentralized Discovery</h2>
+<p>AI Catalog enables decentralized discovery: any domain can publish its
+MCP servers at <code>/.well-known/ai-catalog.json</code> without registering with a
+central authority.</p>
+<p>A vendor hosting its own MCP servers can publish:</p>
+<pre><code>https://api.acme-corp.com/.well-known/ai-catalog.json
+</code></pre>
 <p>A client discovering MCP servers follows this flow:</p>
 <ol>
 <li>Fetch <code>/.well-known/ai-catalog.json</code> to discover all artifacts on
    a domain (MCP servers, A2A agents, plugins, etc.).</li>
-<li>Filter entries by <code>type</code> to find MCP servers.</li>
+<li>Filter entries by <code>type</code> (<code>application/mcp-server-card+json</code>) to find
+   MCP servers.</li>
 <li>Evaluate the Trust Manifest for publisher identity and attestations.</li>
 <li>Fetch the Server Card at the entry's <code>url</code> for operational details
    (transport, capabilities, tools, authentication).</li>
@@ -2113,6 +2001,26 @@
 protocol-specific operational details. A domain with multiple MCP
 servers publishes one AI Catalog listing all of them, with each entry
 pointing to its respective Server Card.</p>
+</section>
+<section id="what-ai-catalog-adds">
+<h2>What AI Catalog Adds</h2>
+<p>A Server Card describes a single server but has no cross-server discovery
+or trust layer. AI Catalog fills this gap:</p>
+<ol>
+<li><strong>Publisher identity</strong>: Verifiable publisher with DID or domain
+   anchor.</li>
+<li><strong>Trust verification</strong>: Attestations (SOC2, HIPAA, publisher
+   identity proofs) via the Trust Manifest.</li>
+<li><strong>Provenance</strong>: Links to source repositories, registries, and
+   build artifacts with cryptographic digests.</li>
+<li><strong>Signing</strong>: Detached JWS signature on the Trust Manifest for
+   integrity verification.</li>
+<li><strong>Cross-ecosystem discovery</strong>: MCP servers become discoverable
+   alongside A2A agents, plugins, and datasets through a single
+   catalog format.</li>
+<li><strong>Composability</strong>: MCP servers can be packaged with related
+   artifacts (A2A agents, datasets) in nested catalogs.</li>
+</ol>
 </section>
 </section>
 <section class="appendix" id="mapping-to-claude-code-plugins-marketplace">
