Back to Gap Map Organization

Silverhand

company

Scores

1 product on the map — 1 open.

MCP Auth

Openness

5 high confidence
5.0
license
MIT (Node.js SDK in mcp-auth/js and Python SDK in mcp-auth/python)
source
public
core features withheld
no — the trees at 8e1b349 for mcp-auth/js, 49 paths, and 4234fed for mcp-auth/python, 45 paths, each carry one MIT LICENSE with no ee/, enterprise/, commercial/ or proprietary/ path; Silverhand sells Logto Cloud, a separate identity service, and the library works with any compliant OAuth or OpenID Connect provider
commercial
Logto-Cloud

Both SDKs are MIT licensed, and the published code is the whole library: it verifies tokens locally against whichever provider the server trusts. Silverhand's paid product is Logto Cloud, a separate identity service that MCP Auth does not require.

Adoption

2 medium confidence
2.0

Adoption is counted as npm downloads of mcp-auth and PyPI downloads of mcpauth over the trailing month, the two SDKs' own packages, most of them for the Node.js SDK. Downloads include build and CI installs and cannot show how many MCP servers run behind the library.

Capability

1 medium confidence
1.0

MCP Auth checks the token on every request and, where a server asks for it, the scopes a single tool requires before the tool runs. The identity it verifies is the user's rather than the agent's, and it has no delegation chain, approval step or signed record of its decisions.

  • https://mcp-auth.dev/docs recorded 2026-11-20

    The token verifier checks "signature, issuer, audience, expiration, and the claims MCP servers need"; tool callbacks take "{ requiredScopes: [...] }" "for per-tool authorization"; the subject is "the sub claim, typically the user ID".

  • https://raw.githubusercontent.com/mcp-auth/js/master/README.md recorded 2026-11-20

    The Node.js SDK implements "RFC 9728 Protected Resource Metadata and RFC 8707 audience-bound token validation — for any OAuth 2.0 / OpenID Connect provider."