Server
Hugging Face
- Endpoint
https://hf.co/mcp- Transport
- Streamable HTTP
- Access
- Public Anyone can connect; where an account is needed, anyone can create one by self-service sign-up. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · Anonymous users get a standard tool set; logged-in users get their configured tools and Spaces.
- Auth
- No authentication The listed endpoint accepts requests without any credential. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · Token-less requests continue with the anonymous tool set; an HF token as bearer header or OAuth login via ?login are optional.
- Why it is listed
- Listed because it appears in a public directory of MCP servers. Source
- Homepage
- https://huggingface.co
Against MCP Authorization 2026-07-28current
- Not applicable 23
Passive scannot scanned yet · Report
Older revisions of the matrix: 2025-11-25
MCP server features 13
| Feature | Level | Status | Observed | Evidence |
|---|---|---|---|---|
| Protected Resource Metadata served | MUST | Not applicable | source | |
| PRM lists an authorization server | MUST | Not applicable | source | |
| PRM lists scopes_supported | MAY | Not applicable | source | |
| PRM reachable at a well-known URI | MUST | Not applicable | source | |
| resource_metadata in the 401 challenge | MUST | Not applicable | source | |
| 403 insufficient_scope for step-up | SHOULD | Not applicable | source | |
| Scope in the WWW-Authenticate challenge | SHOULD | Not applicable | source | |
| No offline_access in advertised scopes | SHOULD | Not applicable | source | |
| 401 for missing or invalid tokens | MUST | Not applicable | source | |
| Audience validation | MUST | Not applicable | source | |
| Bearer token only in the Authorization header | MUST | Not applicable | source | |
| No token passthrough to upstream APIs | MUST | Not applicable | source | |
| Per-client consent on proxy servers | MUST | Not applicable | source |
Authorization server features 10
| Feature | Level | Status | Observed | Evidence |
|---|---|---|---|---|
| Metadata issuer matches the discovery URL | MUST | Not applicable | source | |
| Authorization server metadata discoverable | MUST | Not applicable | source | |
| Client ID Metadata Documents supported | SHOULD | Not applicable | source | |
| Dynamic Client Registration offered | MAY | Not applicable | source | |
| Documented pre-registration path | SHOULD | Not applicable | source | |
| Issuer identifier in authorization responses | SHOULD | Not applicable | source | |
| PKCE with S256 advertised | MUST | Not applicable | source | |
| Refresh token rotation for public clients | MUST | Not applicable | source | |
| Resource indicators honoured | MUST | Not applicable | source | |
| All endpoints served over HTTPS | MUST | Not applicable | source |