{"version":"2.1.227","anchor":"recognizer-for-a-session-metadata-endpoint","canonical_anchor":"recognizer-for-a-session-metadata-endpoint","heading":"Recognizer for a session metadata endpoint","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/recognizer-for-a-session-metadata-endpoint","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Recognizer for a session metadata endpoint\n\nA matcher for a new session metadata endpoint exists but nothing calls it.\n\n**What**\n\nA new helper matches URLs on the session-ingress host used at startup whose path is exactly a new MCP metadata path. The host is captured once at startup into a holder that can be reset. Nothing in the build was found to call the recognizer, so what it gates is not visible from here.\n\n**Evidence**\n\n`\/v2\/ccr-sessions\/-\/meta\/mcp`\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}