Menu

I scanned 229,539 MCP tool parameters. Here's how many can move your money.
πŸ“°

I scanned 229,539 MCP tool parameters. Here's how many can move your money.

DEV Community: apiΒ·correctoverΒ·10 days ago
#F64da1xD
#devtoapi#devto#dev#servers#census
Reading 0:00
15s threshold

Body:

We froze a SHA-256-anchored census of the public MCP ecosystem on 2026-10-12:

42,163 servers, 229,539 tool parameter schemas. Every number below recomputes

from the frozen exports (screening script, CC0):

3,456 servers ship a funds-movement surface. 1,301 of them have write polarity β€” tools that can move money, not just read balances.

2,663 servers combine money AND credential handling in one trust boundary. If a prompt injection lands on one of these, the blast radius is "spend" not "read".

9,761 servers touch account identity data in tool parameters.

The uncomfortable part: this is only the public ecosystem. Enterprise-internal

MCP deployments β€” invisible to any census β€” are where the regulated traffic

actually lives.

What we did about it (and what you can reuse, CC0):

A risk gazetteer schema where every label must carry an evidence chain (frozen parameter path + vocabulary rule ref). No naked labels β€” an unlabeled claim is unverifiable and must be omitted.…

Continue reading β€” create a free account

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