_meta keys avoid prefixes reserved for MCP
Any _meta prefix whose second label is mcp or modelcontextprotocol is reserved for the specification and official extensions; a server should use its own reverse-DNS prefix such as com.example/.
Check spec-meta-reserved · MCP specification 2026-07-28 · default severity: advice · rubric 2.1.0
What fails
Keys under a reserved prefix are only for the specification and official extensions. If this key is not defined by one of them, it collides with the protocol's own namespace.
The rule
Any prefix where the second label is
modelcontextprotocolormcpis **reserved** for MCP use.Source: MCP specification 2026-07-28: Overview (JSON Schema usage, _meta, icons)
How to fix it
Use your own reverse-DNS prefix, for example "com.example/".
- Find keys starting with io.modelcontextprotocol/, dev.mcp/ or similar.
- Unless an official extension defines the key, move it under your own prefix.
- Update clients that read the old key.
TypeScript SDK
import { McpServer } from '@modelcontextprotocol/server';
import * as z from 'zod';
const server = new McpServer({ name: 'issues', version: '1.0.0' });
server.registerTool(
'get_issue',
{
title: 'Get issue',
description: 'Return one issue by ID. Use when the user names an issue.',
inputSchema: z.strictObject({
issue_id: z.string().describe('Issue ID, for example ISS-42'),
}),
annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
_meta: { 'com.example/ui-group': 'issues' },
},
async ({ issue_id }) => ({ content: [{ type: 'text', text: 'Done' }] }),
);Python SDK
from typing import Annotated
from pydantic import Field
from mcp.server.mcpserver import MCPServer
from mcp.types import ToolAnnotations
server = MCPServer("issues")
@server.tool(
title="Get issue",
annotations=ToolAnnotations(readOnlyHint=True, destructiveHint=False, openWorldHint=False),
meta={"com.example/ui-group": "issues"},
)
def get_issue(
issue_id: Annotated[str, Field(description="Issue ID, for example ISS-42")],
) -> str:
"""Return one issue by ID. Use when the user names an issue."""
return "Done"Run against @modelcontextprotocol/server 2.4.0, mcp 2.3.0 and fastmcp 4.2.2 on 2026-11-18; the checker confirms this check passes on the tool list each snippet produces.
Questions
Why reserve prefixes?
So future protocol keys never collide with a server’s own. A server that uses io.modelcontextprotocol/ for its own data may break when the protocol defines that key.
Is this a blocking problem?
No, the checker rates it as advice. It becomes a problem only if the protocol later defines the same key.
Related checks
- _meta keys follow the key-name grammar
- No tool-level execution field from 2025-11-25
- Tool fields have the types the schema defines
- All checks in MCP specification 2026-07-28: tools/list rules
How this check is graded
It counts toward: MCP specification 2026-07-28. See the rubric.
Last verified against MCP specification 2026-07-28: Overview (JSON Schema usage, _meta, icons) on 2026-11-18. The rule above is quoted in the source’s own words. This page as Markdown.
Check your tool list: paste your tools/list, nothing is sent anywhere