mcp-auth

MCPcommunity
v0.2.0Silverhand Inc.MITUpdated 8mo agonpmGitHub

Plug and play auth for Model Context Protocol (MCP) servers

The MCP specification requires OAuth 2.1 and other RFCs for authorization. Instead of implementing all the OAuth 2.1 and OpenID Connect standards yourself, a production-ready provider and a set of libraries and tutorials can save you a lot of time and effort. That's where MCP Auth comes in. It includes: 1. An updated OAuth 2.1 and OpenID Connect provider list that meets the MCP requirements. 2. A…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
51GitHub stars
4Forks
8mo agoLast update
Package
AuthorSilverhand Inc.
LicenseMIT
Version0.2.0
Sourcenpm
npmmcp-auth
GitHubmcp-auth/js
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
ProvenanceAttested · unverified by Forge
Dependencies✓ 17 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 42 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

The MCP specification requires OAuth 2.1 and other RFCs for authorization. Instead of implementing all the OAuth 2.1 and OpenID Connect standards yourself, a production-ready provider and a set of libraries and tutorials can save you a lot of time and effort. That's where MCP Auth comes in. It includes: 1. An updated OAuth 2.1 and OpenID Connect provider list that meets the MCP requirements. 2. A set of provider-agnostic libraries and tools to help you integrate your MCP server with any compli

Keywords
modelcontextprotocolmcpoauthopenidconnectoidc
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.