# _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. Last verified against MCP specification 2026-07-28: Overview (JSON Schema usage, _meta, icons) on 2026-11-18.

## 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 `modelcontextprotocol` or `mcp` is **reserved** for MCP use.

Source: [MCP specification 2026-07-28: Overview (JSON Schema usage, _meta, icons)](https://modelcontextprotocol.io/specification/2026-07-28/basic/index#_meta)

## How to fix it

Use your own reverse-DNS prefix, for example "com.example/".

1. Find keys starting with io.modelcontextprotocol/, dev.mcp/ or similar.
2. Unless an official extension defines the key, move it under your own prefix.
3. Update clients that read the old key.

### TypeScript SDK

```ts
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

```python
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"
```

## 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](https://isokron.ai/mcp-check/checks/spec-meta-key)
- [No tool-level execution field from 2025-11-25](https://isokron.ai/mcp-check/checks/spec-execution-legacy)
- [Tool fields have the types the schema defines](https://isokron.ai/mcp-check/checks/spec-field-types)
- [MCP specification 2026-07-28: tools/list rules](https://isokron.ai/mcp-check/checks/protocol)

Counts toward: MCP specification 2026-07-28.

Rubric: https://isokron.ai/mcp-check/rubric

Check your tool list: https://isokron.ai/mcp-check
