MCP Server(s) Discoverability

[kidehen]

Problem
Discoverability of MCP servers currently relies on a growing number of registries. This approach is not scalable and inevitably leads to a dominant registrar that risks becoming a market choke point.

Solution
Adopt an IANA-registered link relation embedded in the HTML documents of MCP server providers. Similar to how RSS and Atom enabled federated content discovery during the blogosphere era, this method supports a loosely coupled, registry-independent approach to MCP server discovery.

Implementation
The following entry in an MCP server provider’s HTML page is all that’s needed to support this as a recommended best practice:

<link rel="service" href="https://api.example.com/mcp">

[kavinkumar807]

@mrexodia I will check with this

[olaservo]

This issue was resolved with PR #480 .