MCPJacking Exposes 155 Stale MCP Registry Entries to Domain Takeovers
Emerging Technology Risk · 3 sources · Updated 3mo ago · First seen Sep 3, 2026

AIR Security researchers identified 155 Model Context Protocol (MCP) servers in the Official MCP Registry whose underlying services were offline while their associated domains had expired. An attacker can re-register one of those domains and operate a malicious server at the trusted registry address, potentially causing AI agents that retain the stale MCP configuration to connect to attacker-controlled infrastructure.
A hijacked MCP server could alter tool definitions, inject prompts, redirect agent actions, and exfiltrate data available to the agent. The exposure highlights unresolved MCP supply-chain weaknesses, including insufficient runtime endpoint verification, unsigned or unpinned server dependencies, and permissive tool execution; organizations should inventory MCP integrations, remove stale entries, verify and pin server identities, enforce least privilege and approval controls, and govern access through allowlists, internal registries, and monitoring.


