Hey — I'm Ali, solo founder here. I built getmcpauth because I kept seeing MCP servers ship with no auth at all, or with a hand-rolled API key check that technically works but isn't OAuth. To get a real read on how common this is, I sampled 97 public MCP servers from directories. 87 responded; 9 (about 10%) accepted zero-auth requests. Not huge, but not zero — enough to convince me this is a real, recurring gap. getmcpauth hosts the fiddly part (token minting, RFC 8414 discovery, RFC 7591 client registration) so you don't have to implement it. Wire in the npm SDK, or if you've already got users, call mintToken() server-to-server instead. It's early and solo-built — rough edges expected. Free tier exists so you can try it without a sales call. I'd genuinely like feedback, especially from anyone who's implemented MCP auth by hand and hit something painful.

getmcpauth: OAuth 2.1 for MCP servers

Hosted OAuth 2.1 + DCR for MCP servers

Hosted OAuth 2.1 + DCR for MCP servers