AIDEFEND in Action AIA-0142 Research

McPhantom: Coding Agents Bring Retired MCP Servers Back

Glow Labs observed coding assistants installing retired MCP reference servers during ordinary setup work. The important operational gap is that a locally launched package can escape repository-only dependency inventories. The report supports tighter package and server admission, not a claim that those sessions were malicious intrusions.

Remote Code ExecutionPackage VettingMCP SecurityAI Coding Agent
4 applicable AIDEFEND defenses

Threat Analysis

  • A real package can still be the wrong choice: Glow observed agents selecting and setting up retired reference servers during ordinary coding work. The researchers attribute most selections to stale model knowledge, but the transcripts do not expose the model’s training provenance. The reported 98% is limited to sessions that installed a deprecated server.
  • The maintenance boundary is explicit: The maintainers’ archived repository says it provides no further security updates or bug fixes. A package can remain downloadable after that decision. Inventory must therefore identify the actual local implementation, not only the service name or the presence of a Node process.
  • Keep exploitation claims bounded: Glow reports additional flaws, including a Puppeteer execution risk, but says it has not observed exploitation and that the setup sessions did not involve malicious actors. This account does not reconstruct an unpublished exploit or treat download totals as compromised machines. Supporting primary records: the maintainers’ retirement notice.

Applicable AIDEFEND Defenses (4)

AID-H-022.002
Pre-Merge Dependency Change Risk Review
High
Treat an agent-proposed MCP configuration or installation as a dependency change before allowing it to merge or become the approved endpoint configuration. Verify the actual package repository, maintainer, archive/deprecation status, install behavior and current replacement. A formal review path must also cover changes written directly by an agent; a PR-only check cannot see an unreviewed local npx launch.
AID-H-003.001
Software Dependency & Package Security
High
Resolve approved MCP packages and their transitive dependencies into a version-and-integrity-bound installation population, using the npm equivalent of the framework’s Python lock example. Reject disallowed retired packages and unreviewed network resolution at installation time. Pinning an old vulnerable version without a current approval policy simply makes the unsafe choice repeatable.
AID-H-003.010
Deployed AI Software Vulnerability Remediation Lifecycle
High
Inventory actual local MCP configurations, resolved package locations and running process identities across managed endpoints, then join them to current primary advisories and maintenance status. Include packages launched from npx caches even when no project manifest lists them. Record uncovered endpoints and unsupported package ecosystems as missing evidence, not a clean fleet. When an archived server has no repair, disable its use and replace it with a reviewed maintained implementation, verifying every affected endpoint. If temporary use is unavoidable, require an owner, enforced scope restriction, expiry and replacement plan; an unexpired exception is still open risk. Removing a configuration entry alone does not prove an already running process stopped or that a second client cannot relaunch it.
AID-H-024.001
Fully Qualified Tool ID & Version Pinning
Medium
A managed tool resolver should accept only the exact approved tool namespace and version from a protected allowlist, then bind that selection to the approved MCP implementation. Remove retired references and deny bare names or fallback substitutions. This requires a resolver/launcher integration across each client; a friendly display name or a signed list that no launcher enforces is insufficient.

What Defenders Should Do Now

  • Review MCP additions as dependency changes, check primary maintenance status and approve a specific maintained implementation. Route direct endpoint changes through the same controls as repository changes.
  • Bind installation to reviewed package identities, versions and bytes; do not let a launcher resolve a floating package outside admission. Use an enforced approved tool catalog and verify each client’s local, project, plugin and managed scopes.
  • Find existing retired packages through actual endpoint configuration and process inventory. Disable and replace them, confirm relaunch is blocked, and time-bound any remaining exception. Native controls such as Claude Code managed MCP settings are product-specific examples, not a universal setting for all agents. Supporting primary records: Claude Code’s managed MCP policy documentation.

Conclusion

AIDEFEND  turns this observation into four practical responsibilities: review the proposed dependency, admit the exact package bytes, resolve only approved tool versions and maintain the deployed fleet. The result depends on controls that cover local installations and remain effective when an agent suggests the retired server again.

Last updated: