MCP (Model Context Protocol) crossed 97 million monthly SDK downloads. Every major AI provider adopted it. It solved a real problem: how do agents invoke tools and retrieve context in a standardized way? But MCP is a protocol for what agents can do. It says nothing about where they are or how they find each other. Your MCP server lives at a URL. That URL is hardcoded in your agent's config. If it changes, your agent breaks. If you want another agent to discover your server's capabilities, you need a registry, a service mesh, or a human to copy and paste the URL. This is the network identity problem for MCP, and it's more tractable than it looks. What MCP Actually Does (and Doesn't Do) MCP standardizes the tool-calling layer. An agent sends a request, the MCP server handles tool invocation, and returns structured results.…