Is MCP Mermaid safe to use?

MCP Mermaid has an HVTrust score of 45.2/100 (Grade D), ranked #904 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Mermaid?

MCP Mermaid scores 45.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 628 GitHub stars and is categorized under MCP Servers.

MCP Mermaid

hustcc/mcp-mermaid

❤️ Generate mermaid diagram and chart with AI MCP dynamically.

MCP Servers TypeScript Grade D Listed MIT

45.2/100

Rank #904 of 1320

Compare MCP Mermaid

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-05-15 · 112d ago

Recent change

Rank +9

Is MCP Mermaid safe? MCP Mermaid scores 45.2/100 (Grade D), ranked #904 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.8/10; 100% of recent commits are signed; last pushed 2026-05-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#489 MCP Neo4j — 45.3 (D) → #490 Kolada MCP Server — 45.2 (D) → #492 NotebookLM MCP (PleasePrompto) — 45.2 (D) → #493 ASP.NET Core Debugger — MCP Server for AI Agents — 45.1 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 16 spots (#888 → #904)

2026-09-03

Rank Moved

Rank dropped 54 spots (#834 → #888)

2026-09-02

Rank Moved

Rank dropped 42 spots (#792 → #834)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Refresh maintenance signals The repo was last pushed 112 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Mermaid View MCP Servers Report missing data

34.4

Activity sub-score · out of 100

#491

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

628

Forks

Last Push

2026-05-15

112 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼16

was #888

Analysis

HVTrust Dimensions vs MCP Servers

45.2 / 100 · 100.0% confidence

MCP Mermaid MCP Servers average (778 agents)

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

9.8 / 25

in line with avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

4.5 / 20

7.7 below avg 12.2

AdoptionLog-scaled stars · package downloads

6.7 / 20

in line with avg 6.2

Activity Inputs

34.4 / 100

StarsRepository reach

16.8 / 30

FreshnessLast push recency

9.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.8 / 10

OpenSSF Scorecard · scanned Sep 3, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 6

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Is MCP Mermaid safe?

Public trust evidence for MCP Mermaid is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does MCP Mermaid publish package provenance?

No published build provenance is currently detected for MCP Mermaid. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Mermaid have an OpenSSF Scorecard?

MCP Mermaid has an OpenSSF Scorecard score of 3.8/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 MCP Mermaid actively maintained?

Slowing down. Last push was 112 days ago — keep an eye on whether activity resumes.

What license does MCP Mermaid use?

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

Are MCP Mermaid's commits signed?

100% of the last 100 commits to MCP Mermaid 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

MCP Mermaid appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

browser

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 MCP Mermaid'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-08-13

Activity Went Stale

No commits for 90 days

Maintain MCP Mermaid?

For maintainers

HVTrust scores MCP Mermaid 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-09-04

Rank Moved

Rank dropped 16 spots (#888 → #904)

2026-09-03

Rank Moved

Rank dropped 54 spots (#834 → #888)

2026-09-02

Rank Moved

Rank dropped 42 spots (#792 → #834)

2026-09-01

Rank Moved

Rank dropped 33 spots (#759 → #792)

2026-08-31

Scorecard Added

OSSF Scorecard: 3.8/10

2026-08-31

Rank Moved

Rank rose 462 spots (#1221 → #759)

2026-08-31

HVTrust Changed

HVTrust up 25.8pts (19.7 → 45.5)

2026-08-30

Rank Moved

Rank dropped 19 spots (#1202 → #1221)

2026-08-29

Rank Moved

Rank dropped 22 spots (#1180 → #1202)

2026-08-28

Rank Moved

Rank dropped 20 spots (#1160 → #1180)

2026-08-27

Rank Moved

Rank dropped 14 spots (#1146 → #1160)

2026-08-26

Rank Moved

Rank dropped 53 spots (#1093 → #1146)

2026-08-24

Rank Moved

Rank dropped 10 spots (#1077 → #1087)

2026-08-17

Rank Moved

Rank rose 11 spots (#1082 → #1071)

2026-08-16

Rank Moved

Rank dropped 33 spots (#1049 → #1082)

2026-08-13

Activity Went Stale

No commits for 90 days

2026-08-13

Rank Moved

Rank dropped 11 spots (#1040 → #1051)

2026-08-12

Rank Moved

Rank rose 17 spots (#1057 → #1040)

2026-08-10

Rank Moved

Rank dropped 66 spots (#988 → #1054)

2026-08-08

Newly Listed

First tracked at rank #981

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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