Analysis
A First Measurement Study on Authentication Security in Real-World Remote MCP Servers
First reported · Discovered arxiv.org
Page published
Earliest dated coverage: 22 Sep 2026 · First observed: 9 Nov 2026 · Latest dated coverage: 22 Sep 2026
Coverage timeline
Single-source analysis — one report is available.
Why it matters
MCP-connected browser agents require explicit authentication, constrained permissions, and maintained SDKs because their tools can combine authenticated sessions, attacker-controlled content, and code execution.
TestDino's MCP security guide synthesizes published authentication studies, SDK security advisories, and guidance on constraining Playwright-connected agents. A cited measurement study found that 40.55% of 7,973 live remote MCP servers exposed tools without authentication, while the guide highlights risks from browser credentials, untrusted page instructions, and code-execution capabilities.