Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.260,
ImprovementsSection of the release
When resolving a capability manifest's MCP server entries against a first-party host id, the resolver now also checks whether a locally-configured server's name (or its normalized form) matches that host. If it does, the manifest entry is treated as referring to that local server (local_server_as_first_party) instead of being flagged as unresolved or opaque.