This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
getmcpauth: OAuth 2.1 for MCP servers
Hosted OAuth 2.1 + DCR for MCP servers
Hosted OAuth 2.1 authorization server for MCP servers, with RFC 7591 Dynamic Client Registration and RFC 8414 discovery built in. Drop in the npm SDK and clients like Claude can register and authenticate automatically — no auth server to build yourself. We checked 87 real public MCP servers from Glama, PulseMCP, Smithery, and mcp.so — 9 (10%) had zero authentication. getmcpauth closes that gap. Free tier included, no sales call.
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.
About getmcpauth: OAuth 2.1 for MCP servers on Product Hunt
“Hosted OAuth 2.1 + DCR for MCP servers”
getmcpauth: OAuth 2.1 for MCP servers was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #123 on the daily leaderboard. Hosted OAuth 2.1 authorization server for MCP servers, with RFC 7591 Dynamic Client Registration and RFC 8414 discovery built in. Drop in the npm SDK and clients like Claude can register and authenticate automatically — no auth server to build yourself. We checked 87 real public MCP servers from Glama, PulseMCP, Smithery, and mcp.so — 9 (10%) had zero authentication. getmcpauth closes that gap. Free tier included, no sales call.
On the analytics side, getmcpauth: OAuth 2.1 for MCP servers competes within API, Developer Tools and Security — topics that collectively have 616.5k followers on Product Hunt. The dashboard above tracks how getmcpauth: OAuth 2.1 for MCP servers performed against the three products that launched closest to it on the same day.
Who hunted getmcpauth: OAuth 2.1 for MCP servers?
getmcpauth: OAuth 2.1 for MCP servers was hunted by Ali. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of getmcpauth: OAuth 2.1 for MCP servers including community comment highlights and product details, visit the product overview.
Ali