Symptom
The MCP server picker shows, e.g.:
jira · official · https://waystation.ai/jira/mcp
Track issues, manage projects, and streamline workflows in Jira.
Read in context — a product name, a product description, and an "official" badge — this presents as Atlassian's official Jira server. It is not: the registry entry is ai.waystation/jira, a third-party proxy that happens to be named after the product it fronts.
What the badge actually asserts
resolve_candidates (backend/druks/mcp/registry.py) sets official when the publisher provably owns the remote's domain: the reversed namespace (ai.waystation → waystation.ai) matches the remote URL's host, or a repo pin vouches. That is publisher authenticity — "this endpoint really belongs to the namespace owner" — not vendor endorsement.
The two collide exactly when a third party registers a server named after someone else's product, which the registry legitimately allows within an owned namespace. The badge then amplifies the confusion instead of resolving it: the case where a user most needs to notice "my data flows through a third party" is the case where the UI says "official".
Proposed fix
Surface who is verified rather than a bare badge — e.g. render verified: waystation.ai (the proven domain) instead of official. The trust computation is already correct; only its label overclaims. Optionally distinguish the derived display name from the registry namespace in the picker row so ai.waystation/jira is visible without expanding anything.
Symptom
The MCP server picker shows, e.g.:
Read in context — a product name, a product description, and an "official" badge — this presents as Atlassian's official Jira server. It is not: the registry entry is
ai.waystation/jira, a third-party proxy that happens to be named after the product it fronts.What the badge actually asserts
resolve_candidates(backend/druks/mcp/registry.py) setsofficialwhen the publisher provably owns the remote's domain: the reversed namespace (ai.waystation→waystation.ai) matches the remote URL's host, or a repo pin vouches. That is publisher authenticity — "this endpoint really belongs to the namespace owner" — not vendor endorsement.The two collide exactly when a third party registers a server named after someone else's product, which the registry legitimately allows within an owned namespace. The badge then amplifies the confusion instead of resolving it: the case where a user most needs to notice "my data flows through a third party" is the case where the UI says "official".
Proposed fix
Surface who is verified rather than a bare badge — e.g. render
verified: waystation.ai(the proven domain) instead ofofficial. The trust computation is already correct; only its label overclaims. Optionally distinguish the derived display name from the registry namespace in the picker row soai.waystation/jirais visible without expanding anything.