ModelContextPro.dev / Specification
SPECIFICATION · MCP 2026-07-28

MCP 2026-07-28 Stateless Transport & Tool Security Spec

Normative checklist for deploying horizontal, edge-safe Model Context Protocol servers without sticky memory sessions or ambiguous tool descriptions.

1. Stateless Streamable HTTP Invariants

Under the 2026-07-28 MCP profile, every tool call must be independently authenticatable and replay-safe across edge workers or autoscaled replicas:

2. Canonical tools/list Contract

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tools": [
      {
        "name": "dns_record_lookup",
        "description": "Read-only lookup of A, AAAA, CNAME, and TXT records for one hostname.",
        "annotations": { "readOnlyHint": true, "destructiveHint": false, "idempotentHint": true },
        "inputSchema": {
          "type": "object",
          "additionalProperties": false,
          "required": ["hostname"],
          "properties": {
            "hostname": { "type": "string", "pattern": "^[a-z0-9.-]{3,253}$" }
          }
        }
      }
    ]
  }
}

3. Tool-Poisoning & Shadowing Defense

Threat ClassDetection RuleRemediation
Prompt injection in descriptionImperative overrides (ignore previous, hidden XML/HTML tags, base64 payloads)Restrict descriptions to plain declarative 1–2 sentence summaries under 280 chars.
Destructive tool without guardTool name matches delete|drop|purge|transfer with destructiveHint unsetDeclare explicit annotations.destructiveHint: true and require policy gate before execution.
Unconstrained object input"type": "object" missing properties or additionalProperties: falsePin every parameter type, enum, and required array so callers cannot smuggle extra keys.

Interoperability Cluster

Compile validated MCP tools to A2A v1.0.1 on a2amcp.dev →