ards-project · rvguha · Jun 3, 2026
diff --git a/docs/README.md b/docs/README.md
@@ -106,5 +106,3 @@ Use an **anti-hype, high-density, clinical tone**:
 
 - **Spec and product discussion:** [agentfinder-project/agentfinder issues](https://github.com/agentfinder-project/agentfinder/issues)
 - **Documentation changes:** Open a PR in this repository (`agentfinder-project/docs`). Public write access may be limited; ask in issues or [Discord](https://discord.gg/PK3DpEybzP) if you need collaborator access.
-
-See also [Contributors](contributors.md) on the published site.
diff --git a/docs/anthropic_mcp.md b/docs/anthropic_mcp.md
diff --git a/docs/comparisons.md b/docs/comparisons.md
@@ -12,24 +12,8 @@ Agent Finder is designed as a **superset** of existing agent and tool discovery
 
 ## What about...
 
-### What about MCP Registry
-
-The entire list of public MCP servers can be indexed natively. The official MCP Registry (`registry.modelcontextprotocol.io`) can remain exactly as it is today, while also acting as a federated source of truth that is crawled and made queryable via Agent Finder search endpoints.
-
-`TODO(Guha): please fill in`
-
----
-
 ### What about ACP Agent Registry
 
 The list of ACP Agents in [ACP's Agent Registry](https://agentclientprotocol.com/get-started/registry) is already structurally close to the AI Catalog specification. ACP registries can easily export their directory manifests as standard `ai-catalog.json` feeds, enabling instant web-scale discovery for editor-context tools.
 
-`TODO(Guha): please fill in`
-
----
-
-### What about Open Plugins
-
-A plugin under the [Open Plugins](https://open-plugins.com/) standard is essentially a bundle of MCP servers, Skills, or other tools. By describing these bundles inside the standard AI Catalog specification, Open Plugins can leverage Agent Finder's federated infrastructure for instant decentralized deployment, crawling, and semantic indexing.
-
-`TODO(Guha): please fill in`
+`TODO(Guha): please fill in`
diff --git a/docs/contributors.md b/docs/contributors.md
diff --git a/docs/how_to_build_search.md b/docs/how_to_build_search.md
@@ -5,7 +5,7 @@
 
 A Search Registry is an active service that crawls static manifests, indexes capabilities semantically, and exposes standard REST search endpoints (`POST /search`) to clients.
 
-Building your own Search Registry is entirely optional. If you only want to publish capabilities, you only need to host a static manifest (see [How to Publish](how_to_publish.md)). To query capabilities, your client can connect to any existing public or private search registry (see [Implementations](implementations.md) for active endpoints).
+Building your own Search Registry is entirely optional. If you only want to publish capabilities, you only need to host a static manifest (see [How to Publish](how_to_publish.md)). To query capabilities, your client can connect to any existing public or private search registry.
 
 ---
 

diff --git a/docs/implementations.md b/docs/implementations.md
diff --git a/docs/introduction.md b/docs/introduction.md
@@ -12,12 +12,9 @@ We have seen this before. In 1994, finding something on the web meant a bookmark
 
 ## The next step
 
-The discovery problem is well recognized, and the work so far has come in two kinds. Toolbox (Microsoft Foundry) and MCP registries provide mechanisms to create curated sets of augments — a vetted collection a developer can point at. ToolLLM (Qin et al., 2023) and Claude's tool-search take a different step: they make selection cheaper by moving part of it out of the context window, retrieving the relevant augments per query rather than injecting all of them.
+The discovery problem is well recognized, and the work so far has come in two kinds. Toolbox (Microsoft Foundry) provides a mechanism to create curated sets of augments — a vetted collection a developer can point at. ToolLLM (Qin et al., 2023) and Claude's tool-search take a different step: they make selection cheaper by moving part of it out of the context window, retrieving the relevant augments per query rather than injecting all of them.
 
-Agent Finder takes the next logical step: **an abstraction layer over both.** It is a protocol, not a product or a particular search engine, and it pins down two things while leaving the rest open: how an augment is described, and how a client asks the discovery question and reads the answer. The service that answers can be built however its provider chooses — including with the very techniques above. This turns the existing curated sets into something a client calls uniformly, so an augment published once is found by many clients, and a client reaches augments far beyond its own pre-connected set.
-
-!!! note "Find, don't invoke"
-    Agent Finder finds, it does not invoke. Discovery returns which augment fits and where to reach it; invocation happens over that augment's own protocol.
+Agent Finder takes the next logical step: **an abstraction layer over both.** It is a protocol, not a product or a particular search engine, and it pins down two things while leaving the rest open: how an augment is described, and how a client asks the discovery question and reads the answer. The service that answers can be built however its provider chooses — including with the very techniques above. This turns the existing curated sets into something a client calls uniformly, so an augment published once is found by many clients, and a client reaches augments far beyond its own pre-connected set. Agent Finder only finds; it does not invoke. Discovery returns which augment fits and where to reach it, and the client then invokes it over the augment's own protocol.
 
 ---
 
@@ -29,8 +26,7 @@ The more consequential case is the **enterprise**. An IT or platform team runs i
 
 Because the protocol allows aggregation across endpoints, control also means **composition**. An IT manager can define their instance as "everything GitHub's Agent Finder serves, plus the augments in our internal one" — a union of a public endpoint and a private one, queried as a single view.
 
-!!! tip "The DNS property"
-    This is a property DNS has and web search does not: DNS resolvers compose, forwarding to upstream servers and merging the global namespace with local zones, so every organization runs its own resolver without leaving the shared system. Web search has no equivalent — you query one engine's index, and there is no standard way to say "these results plus my company's, merged." Agent Finder inherits the DNS property: instances compose, so an enterprise extends the public ecosystem rather than walling itself off from it.
+This is a property DNS has and web search does not: DNS resolvers compose, forwarding to upstream servers and merging the global namespace with local zones, so every organization runs its own resolver without leaving the shared system. Web search has no equivalent — you query one engine's index, and there is no standard way to say "these results plus my company's, merged." Agent Finder has a similar property: instances compose, so an enterprise extends the public ecosystem rather than walling itself off from it.
 
 ---
 
@@ -40,8 +36,7 @@ Agent Finder is exposed to a client as a **Skill**, and equivalently as an **MCP
 
 The other side is **publishing**. Anyone with an augment they want discovered — a single tool or skill, or a whole internal set — describes it in a standard catalog file, hosts it on their own domain, and advertises it via a well-known URL, a `robots.txt` entry, an HTML tag, or DNS. Any Agent Finder–compatible instance can then index those augments. The catalog is published once and reachable by every instance that chooses to include it, rather than integrated separately into each client.
 
-!!! info "Two distinct roles"
-    Publishing a catalog makes an augment *available* to be indexed; running an instance decides what actually gets *served* to a given set of users.
+These are two distinct roles: publishing a catalog makes an augment *available* to be indexed, while running an instance decides what actually gets *served* to a given set of users.
 
 ---
 

diff --git a/docs/open_plugins.md b/docs/open_plugins.md
diff --git a/docs/why.md b/docs/why.md
@@ -26,7 +26,7 @@ Instead of forcing the LLM to sort through the noise, Agent Finder moves selecti
 
 We are moving away from manually installed, hardcoded integrations toward dynamic runtime discovery.
 
-| Vector | Centralized Registries (e.g., MCP Registry) | Federated Search (Agent Finder) |
+| Vector | Centralized Registries | Federated Search (Agent Finder) |
 | :--- | :--- | :--- |
 | **Discovery** | Manual registration / gatekeeper approval | Dynamic crawling and indexing (SEO for agents) |
 | **Hosting** | Single central repository database | Self-hosted on publisher domains |

diff --git a/docs/zed_acp.md b/docs/zed_acp.md
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -79,7 +79,6 @@ nav:
   - About:
     - Why Agent Finder?: why.md
     - Comparisons: comparisons.md
-    - Contributors: contributors.md
     - FAQ: faq.md
     - Introduction: introduction.md
   - Guides:
@@ -89,8 +88,3 @@ nav:
   - Specifications:
     - Agent Finder Spec: spec.md
     - AI Catalog Spec: ai_catalog_spec.md
-  - Ecosystem:
-    - Implementations: implementations.md
-    - Open-plugins: open_plugins.md
-    - Zed's ACP Agent Registry: zed_acp.md
-    - Anthropic's MCP Registry: anthropic_mcp.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -106,5 +106,3 @@ Use an anti-hype, high-density, clinical tone:

		- Spec and product discussion: [agentfinder-project/agentfinder issues](https://github.com/agentfinder-project/agentfinder/issues)
		- Documentation changes: Open a PR in this repository (`agentfinder-project/docs`). Public write access may be limited; ask in issues or [Discord](https://discord.gg/PK3DpEybzP) if you need collaborator access.

		See also [Contributors](contributors.md) on the published site.
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,7 +5,7 @@ @@
     A Search Registry is an active service that crawls static manifests, indexes capabilities semantically, and exposes standard REST search endpoints (`POST /search`) to clients.
-    Building your own Search Registry is entirely optional. If you only want to publish capabilities, you only need to host a static manifest (see [How to Publish](how_to_publish.md)). To query capabilities, your client can connect to any existing public or private search registry (see [Implementations](implementations.md) for active endpoints).
+    Building your own Search Registry is entirely optional. If you only want to publish capabilities, you only need to host a static manifest (see [How to Publish](how_to_publish.md)). To query capabilities, your client can connect to any existing public or private search registry.
     ---
@@ Expand Down @@