MCP tool namespaces are opaque and inconsistent — cannot tell which server a tool belongs to

In one session I had three MCP servers all exposing an ask_question / deepwiki_ask tool, surfaced under three different namespace styles:

• mcp__9763907f-…__ask_question — a directory connector
• mcp__363d8e44-…__ask_question — the official DeepWiki server
• mcp__deepwiki-mcp__deepwiki_ask — my own local server

The two remote servers are namespaced by opaque UUID, the local one by a readable slug, so from the tool name alone I can't tell which server I'm about to call. I called the wrong one and got Authentication required (it turned out to be the paid Devin endpoint). The human-readable identity didn't disambiguate either: one of those UUID servers opens its instructions with "DeepWiki MCP provides AI-powered documentation…" while actually pointing at devin.ai.

Ask: stable, human-readable, consistent namespaces for MCP tools (not UUIDs), and surface the owning server's real name + endpoint alongside its tools so it's obvious which server a tool call goes to.