Menu

1 / 3

The MCP package looked clean. The installed tree did not.

DEV Community·Bindfort·6 months ago
#kaqcdl9t
#security#ai#mcp#supplychain#package
Reading 0:00
15s threshold

We audited 31 MCP server packages across npm and PyPI.

For each one, we ran two checks:

a direct check of the top-level package

a scan of the installed dependency tree

The direct package check found 1 finding.

The installed trees found 69.

Findings by scan view

That difference is the story.

MCP servers are installable tool surfaces. When an operator installs one, the package manager resolves a runtime tree. That tree can contain vulnerable dependencies even when the top-level package has no finding attached to it.

In this run, 11 of 31 installed trees had at least one finding. Across those trees, we saw 54 unique vulnerabilities: 2 critical, 34 high, 28 medium, 4 low, and 1 unknown severity.

This does not mean every finding is exploitable in every deployment.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.