Vendor-published
Auth0 MCP Server MCP server
Auth0 MCP Server: Manage Auth0 applications, APIs, actions, logs, and forms using natural language
Identity and maintenance
| Registry name | com.auth0/mcp |
|---|---|
| Publisher domain | auth0.com |
| Maintainer type | Vendor-published namespace com.auth0 -> auth0.com; no endpoint to match, but the source repository is github.com/auth0, which matches the namespace vendor segment |
| Latest version seen | 0.1.0-beta.10 |
| Last checked | |
| Last changed | Separate from “last checked”: we check far more often than anything changes. |
Enterprise evaluation
Every row below exists whether or not we found an answer. Expand any row to see the exact source and the date. Unknown means undocumented, never unsupported.
| Access and authentication | |
|---|---|
| Authentication required Whether the hosted endpoint accepted a connection with no credentials when we checked. | Not checked |
| OAuth 2.1 authorization Whether the server publishes OAuth discovery metadata a client can follow automatically. | Not checked |
| Dynamic client registration Without it, an IdP administrator must register a client by hand before anyone can connect. | Not checked |
| Documented scopes | Not checked |
| Read and write are separate scopes A single opaque scope means read-only access cannot be granted: approving access approves everything. | Not checked |
| Deployment and transport | |
| Streamable HTTP transport | No Registry checkedno streamable-http remote declared |
| SSE transport | No Registry checkedno sse remote declared |
| Vendor-hosted endpoint Data leaves your network. Where it goes is a question for the vendor's documentation. | No Registry checkedno remote endpoint declared |
| Self-hostable package A published npm, PyPI, container or bundle artifact you can run inside your own perimeter. | Yes Registry checkednpm:@auth0/auth0-mcp-server |
| Supply chain | |
| Public source repository | Yes Registry checkedhttps://github.com/auth0/auth0-mcp-server |
| Open-source license | |
| Repository actively maintained | Yes Vendor checkedlast push 11 days ago GitHub repository — https://github.com/auth0/auth0-mcp-server |
| Package deprecated | Not checked |
| Secret inputs marked as secret Credential-shaped inputs the publisher did not flag as secret may be logged by a client. | Not checked |
| Documented controls | |
| Audit logging documented | Not documented |
| Access controls documented | Not documented |
| Data residency documented | Not documented |
| Data retention documented | Not documented |
What remains unknown
11 of 18 criteria are undocumented. These are the questions to put to the vendor — not conclusions about the product.
- Authentication required — no source found
- OAuth 2.1 authorization — no source found
- Dynamic client registration — no source found
- Documented scopes — no source found
- Read and write are separate scopes — no source found
- Package deprecated — no source found
- Secret inputs marked as secret — no source found
- Audit logging documented — no source found
- Access controls documented — no source found
- Data residency documented — no source found
- Data retention documented — no source found
Questions people ask
- Does the Auth0 MCP Server MCP server require authentication?
- We could not determine this.
- Can I grant read-only access to the Auth0 MCP Server MCP server?
- Not documented. We found no scope list to read.
- Can the Auth0 MCP Server MCP server be self-hosted?
- Yes. The publisher declares npm: @auth0/auth0-mcp-server.