Introducing Dedalus Auth (DAuth)
Today we’re excited to launch Dedalus Auth (DAuth), a new way to secure Model Context Protocol (MCP) servers and marketplaces. Our authentication architecture protects user credentials and solves long-standing security gaps in the MCP landscape.
DAuth is designed specifically for MCP: it’s multi‑tenant, faithful to the MCP specs, and ensures that no one can see your secrets, not even us.
Existing auth implementations are underdeveloped and difficult for smaller developers to implement. API keys and raw secrets are still being passed around with limited protection, making them vulnerable to malicious servers that hijack user credentials.
To build MCPs with production-grade security, developers need to spend weeks becoming security experts to build authentication and security infrastructure. Most don’t bother. But we believe you shouldn't have to compromise on security.
That’s why we developed DAuth, so MCP creators don’t have to reinvent auth infra, and users never have to hand secrets to strangers.
The best thing about DAuth is that it is built in to our SDK, takes minutes to integrate, and doesn't require developers to be security experts.
Security is the bottleneck for MCP adoption
The biggest barrier to deploying AI agents in production is trust.
Recent high-profile security incidents have shown that MCP can be a vulnerable vector of attack for malicious actors. If we’re going to give agents the tools they need to be useful, their permissions must be handled accurately and securely.
When we started building our MCP marketplace, we were disappointed by the state of MCP auth.
MCP standardized around OAuth, but it doesn’t support dynamically passing API keys, forcing existing MCP marketplaces to be OAuth-centric and single-tenant.
In addition, the MCP specs don’t specify how non‑OAuth credentials should be handled. This is a problem because most MCP servers are non-OAuth, as many of the tools developers use are not authenticated by OAuth, like a search API or database credentials.
For developers using those tools, MCP security becomes a chore. To do things the “right way,” you need to create your own OAuth app for every tool. The easier route, storing raw credentials with the host, turns marketplaces into a single vector of attack: one malicious actor can collect thousands of secrets.
No existing MCP authentication solution serves our users security needs. No one else seems to be working on one that will. So we built the missing baseline: secure, multi-tenant auth that doesn’t depend on every tool being OAuth.