
The 8% Problem: MCP Servers That Look Open But Aren't
When I published "41% of MCP Servers Have No Authentication," I was wrong about 8% of them. Not wildly wrong — the servers were accessible, their tool schemas were visible, and to any passive scanner they looked like open systems. But when you actually tried to call a tool, you got this: { "code" : -32603 , "message" : "Authentication required" } This is Tier 2 authentication. The schema is public. The calls are not. What I Was Missing My scanner checked: can I call tools/list ? If yes, and no 401 came back, I marked the server as "no auth." That logic is wrong. tools/list is not protected on Tier 2 servers. It's intentionally public — you're supposed to know what tools exist. The auth happens at the tool call level, when you actually try to do something. Here's what the three tiers actually look like: Tier 1 (Truly Open): tools/list → tools returned. tools/call → real data returned. 198 servers (37.7%). Tier 2 (API-Layer Auth): tools/list → tools returned (public schema). tools/call →
Continue reading on Dev.to
Opens in a new tab




