Back to feed
Dev.to
Dev.to
6/28/2026
I scanned my MCP setup and it scored 0/100. Here's what was wrong.

I scanned my MCP setup and it scored 0/100. Here's what was wrong.

Short summary

A survey of 7,000 public MCP servers revealed critical security gaps: 41% require no authentication, 36.7% are SSRF-vulnerable, and only 8.5% use OAuth. mcp-audit, a free open-source CLI, scans your local MCP config (Claude Desktop, Cursor, VS Code) and flags issues like plaintext secrets, unpinned executables, and context bloat. The author provides concrete fixes: move secrets to env vars, pin versions, scope filesystem access, and add auth to remote servers.

  • 41% of public MCP servers lack authentication; 36.7% are SSRF-vulnerable
  • mcp-audit free tool scans local config and flags security issues
  • Concrete fixes: use env vars for secrets, pin versions, scope filesystem access, add auth

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more