Is Auth0 MCP Server safe to use?

Auth0 MCP Server has an HVTrust score of 80.7/100 (Grade A), ranked #171 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Auth0 MCP Server?

Auth0 MCP Server scores 80.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 122 GitHub stars and is categorized under MCP Servers.

Auth0 MCP Server

Repository

Connect LLMs and AI agents to Auth0 Management APIs via an MCP server. Use natural-language commands to create apps, deploy Actions, and query logs—runs locally and supports interactive tenant authentication for secure Auth0 administration from AI tools/CLIs.

MCP Servers TypeScript Listed MIT

Is Auth0 MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.6 / 10

Provenance Attested

Signed commits 100%

Last push 7d ago

Advisories None known

Compare Auth0 MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Auth0 MCP Server scores 80.7/100 (Grade A), ranked #171 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% of recent commits are signed; no published advisory affects its latest release (@auth0/auth0-mcp-server); last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Auth0 MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 6.6 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +5.1 → 85.8 A · #26 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Auth0 MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/auth0/auth0-mcp-server, MIT, last pushed 2026-11-03. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.6/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies6
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 4

Packaging -1

Pinned-Dependencies 6

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10
Published packages Linked and attested
- npm @auth0/auth0-mcp-server Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @auth0/auth0-mcp-server 0.1.0-beta.19. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-09-02 OSSF Scorecard: 7.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Auth0 MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Auth0 MCP Server compares in MCP Servers

#84 Brandsystem MCP — Brand Guidelines for AI 80.8 +0.1
#85 Copilot Money 80.8 +0.1
#86 Auth0 MCP Server 80.7 this agent
#87 iOS Simulator MCP 80.7 ±0
#88 Bright Data MCP 80.7 ±0

Bars show each HVTrust score; the tick marks Auth0 MCP Server’s 80.7.

Where the 80.7 comes from

HVTrust dimensions vs the MCP Servers average

80.7 / 100 · 100.0% confidence

Auth0 MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.7 / 25

9.9 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

14.1 / 17

1.8 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

11.5 / 20

0.7 below avg 12.2

AdoptionLog-scaled stars · package downloads

10.4 / 20

2.8 above avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-06

Rank Moved

Rank dropped 19 spots (#138 → #157)

2026-11-03

Rank Moved

Rank rose 23 spots (#152 → #129)

2026-11-01

Rank Moved

Rank dropped 15 spots (#134 → #149)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent View MCP Servers Report missing data

44.8

Activity sub-score · out of 100

#86

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

122

Forks

Last Push

2026-11-03

7 days ago

Commits (4 wk)

Downloads (7d)

11,221

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #168

Analysis

Activity Inputs

44.8 / 100

StarsRepository reach

12.5 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.1 / 20

Common questions about Auth0 MCP Server

Public supply-chain signals for Auth0 MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Auth0 MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does Auth0 MCP Server publish package provenance?

Yes. Auth0 MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Auth0 MCP Server have an OpenSSF Scorecard?

Auth0 MCP Server has an OpenSSF Scorecard score of 6.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Auth0 MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does Auth0 MCP Server use?

Auth0 MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Auth0 MCP Server's commits signed?

100% of the last 100 commits to Auth0 MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Auth0 MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Auth0 MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Auth0 MCP Server?

For maintainers

HVTrust scores Auth0 MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-06

Rank Moved

Rank dropped 19 spots (#138 → #157)

2026-11-03

Rank Moved

Rank rose 23 spots (#152 → #129)

2026-11-01

Rank Moved

Rank dropped 15 spots (#134 → #149)

2026-10-20

Rank Moved

Rank rose 10 spots (#142 → #132)

2026-10-19

Rank Moved

Rank dropped 11 spots (#131 → #142)

2026-10-06

Rank Moved

Rank rose 14 spots (#132 → #118)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 691 spots (#815 → #124)

2026-09-23

HVTrust Changed

HVTrust up 53.4pts (28.5 → 81.9)

2026-09-22

Newly Listed

First tracked at rank #815

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-12

Rank Moved

Rank dropped 14 spots (#95 → #109)

2026-09-12

Activity Score Changed

Activity score down 10pts (55 → 45)

2026-09-09

Rank Moved

Rank dropped 18 spots (#77 → #95)

2026-09-06

Rank Moved

Rank dropped 11 spots (#68 → #79)

2026-09-03

Grade Changed

Trust grade C → A

2026-09-03

Rank Moved

Rank rose 528 spots (#595 → #67)

2026-09-03

HVTrust Changed

HVTrust up 28.9pts (54.1 → 83.0)

2026-09-02

Scorecard Added

OSSF Scorecard: 7.0/10

2026-09-02

Grade Changed

Trust grade B → C

2026-09-02

Rank Moved

Rank dropped 362 spots (#233 → #595)

2026-09-02

HVTrust Changed

HVTrust down 14.3pts (68.4 → 54.1)

2026-09-01

Rank Moved

Rank dropped 10 spots (#223 → #233)

2026-08-31

Grade Changed

Trust grade D → B

2026-08-31

Rank Moved

Rank rose 534 spots (#757 → #223)

2026-08-31

HVTrust Changed

HVTrust up 24.0pts (44.5 → 68.5)

2026-08-30

Grade Changed

Trust grade B → D

2026-08-30

Rank Moved

Rank dropped 555 spots (#202 → #757)

2026-08-30

HVTrust Changed

HVTrust down 24.1pts (68.6 → 44.5)

2026-08-29

Rank Moved

Rank dropped 12 spots (#190 → #202)

2026-08-28

Rank Moved

Rank dropped 30 spots (#160 → #190)

2026-08-26

Rank Moved

Rank dropped 18 spots (#135 → #153)

2026-08-25

Rank Moved

Rank rose 10 spots (#145 → #135)

2026-08-24

Grade Changed

Trust grade D → B

2026-08-24

Rank Moved

Rank rose 367 spots (#512 → #145)

2026-08-24

HVTrust Changed

HVTrust up 24.6pts (45.6 → 70.2)

2026-08-22

Grade Changed

Trust grade B → D

2026-08-22

Rank Moved

Rank dropped 372 spots (#142 → #514)

2026-08-22

HVTrust Changed

HVTrust down 24.8pts (70.5 → 45.7)

2026-08-19

Grade Changed

Trust grade D → B

2026-08-19

Rank Moved

Rank rose 375 spots (#512 → #137)

2026-08-19

HVTrust Changed

HVTrust up 24.7pts (46.1 → 70.8)

2026-08-17

Grade Changed

Trust grade B → D

2026-08-17

Rank Moved

Rank dropped 378 spots (#131 → #509)

2026-08-17

HVTrust Changed

HVTrust down 25.2pts (71.3 → 46.1)

2026-08-13

Grade Changed

Trust grade D → B

2026-08-13

Rank Moved

Rank rose 401 spots (#527 → #126)

2026-08-13

HVTrust Changed

HVTrust up 27.0pts (44.5 → 71.5)

GitHub → npm: @auth0/auth0-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/auth0-mcp-server.svg)](https://hvtracker.net/agents/auth0-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/auth0-mcp-server"><img src="https://hvtracker.net/badge/auth0-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Auth0 MCP Server

How Auth0 MCP Server could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Auth0 MCP Server compares in MCP Servers

Where the 80.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Auth0 MCP Server

AI agent surface

Maintain Auth0 MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers