{"version":"2.1.281","anchor":"mcp-apps-html-resources-with-profilemcp-app-are-recognised","canonical_anchor":"mcp-apps-html-resources-with-profilemcp-app-are-recognised","heading":"MCP apps: HTML resources with profile=mcp-app are recognised","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/mcp-apps-html-resources-with-profilemcp-app-are-recognised","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### MCP apps: HTML resources with profile=mcp-app are recognised\n\nHTML resources from MCP servers marked with profile=mcp-app are now recognised as app interfaces\n\n**Unclear.** The finding does not name the address prefix or say what Claude Code does with a resource once it is recognised as an app.\n\n**What**\n\nMCP (Model Context Protocol) is the standard Claude Code uses to connect to outside servers that provide tools and resources. A new check decides whether a resource from such a server is an app's user interface. A resource counts as one when either:\n\n- its address starts with a particular prefix, or\n\n- its type is `text\/html` with a `profile` parameter equal to `mcp-app`.\n\nThe type's parameters are now read properly, including values written in quotes.\n\n**Why**\n\nMCP servers that mark their HTML pages with `profile=mcp-app` are identified as app interfaces even when the address does not use the special prefix.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}