Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

MCPhantom: agents install dead MCP servers

Written November 7, 2026

Your agent asked for a GitHub MCP server and installed an archived one from training data — with four unpatched high-severity flaws. The check, and the fix.

What Glow Labs found

Glow Labs reviewed real coding-agent session transcripts and found agents setting up deprecated MCP servers that Anthropic published as reference implementations when MCP launched. In 98% of the sessions where an agent set up a deprecated server, the agent supplied the old package name from its training data: the developer asked for a capability such as "a GitHub MCP", and the agent filled in the name it already knew instead of looking for the current server. In the other 2%, the user asked for the deprecated package by name and the agent obliged. The pattern showed up in every harness in the data — Claude Code, Cursor, Codex CLI, Anthropic's desktop file agent, and Claude chat — and with models from Anthropic, OpenAI, and xAI, so no single vendor's fix closes the gap. Glow Labs calls the pattern MCPhantom.

The GitHub case shows how it happens. Instead of the MCP server GitHub maintains, the agent picked the archived Anthropic reference server it remembered from training data. That repository is archived, and its archive notice says no security updates or bug fixes will be provided. Anthropic published 20 reference servers when it introduced MCP in 2024; once services shipped servers of their own, 13 of those 20 were archived. The archive is a normal part of a maturing ecosystem — and it means nobody is left to fix the code inside.

The flaws

Four high-severity flaws sit in the archived reference servers, and no fix is coming. The worst is a remote code execution bug in the Puppeteer server, which lets an agent open a browser session. With a prompt injection, an attacker can make the agent start any process on the machine instead of the browser and run any command. The permission the developer granted — letting the agent browse the web — ends up covering any command, so the harness does not stop it. Glow Labs reported the bug and the maintainers replied that the server was archived in May 2025 and is unmaintained, so no fix or release will come from that repository. There is no CVE for these flaws, and Glow Labs has not seen anyone exploit them. That is the whole point of the warning: the door stays open, with no patch coming.

The scale is large. The deprecated servers have 17,352,267 npm downloads since July 10, 2025, and five of them sit in npm's top MCP 100.

PackageDownloads since July 10, 2025
@modelcontextprotocol/server-github5,266,085
@modelcontextprotocol/server-postgres4,312,874
@modelcontextprotocol/server-slack3,198,630
@modelcontextprotocol/server-puppeteer1,487,526
@modelcontextprotocol/server-brave-search1,461,811
@modelcontextprotocol/server-google-maps814,615
@modelcontextprotocol/server-gitlab273,296
@modelcontextprotocol/server-gdrive247,891
@modelcontextprotocol/server-redis131,160
@modelcontextprotocol/create-server122,534

Downloads are not installs on your machines, and they are not evidence that any particular team is exposed. They measure how widely the retired packages still circulate.

Why nothing catches it

The servers never appear in a dependency file, so the tools built to watch dependencies do not see them. A deprecated package disappears from npm search, but npx still installs it with nothing more than a warning.

ControlWhat it watchesWhy it stays quiet
EDRMalicious files and behaviourA trusted Node process installs a public npm package an agent requested.
SCAKnown-vulnerable dependencies in manifestsAn npx-launched server sits in no project manifest, and no CVE exists for these flaws.
Agent harness guardrailsWhat the agent may runThe harness cannot stop it because it does not know the package is deprecated.
Software inventoryInstalled applicationsA server launched by npx runs inside a Node process, so it never shows up as an installed application.

That leaves the endpoint — where the agent writes the config and runs the install — as the one place the problem shows up.

The check and the fix

Search developer machines for MCP configs that reference the deprecated @modelcontextprotocol/server-* packages, and switch to the service owner's own MCP server where one exists. Start with Puppeteer: it carries the remote code execution flaw, and it is the one to remove first. Then approve one MCP server per service and make it the standard, so agents do not revert to outdated training data, and add npm deprecation status to the criteria for approving any MCP server.

A check of the machine used for this page found no MCP config naming a deprecated @modelcontextprotocol/server-* package: the Claude Code settings file lists no MCP servers, and no Codex, Cursor, or Claude Desktop config file was present. The only matches for the package names were documentation examples, not installed servers.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: 140 silent MCP contract changes, and how to pin them · A malicious MCP server probed cloud credentials · MCP reference servers 2.3.0: what's new