Is MeiGen AI Design MCP safe to use?

MeiGen AI Design MCP has an HVTrust score of 54.9/100 (Grade C), ranked #789 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MeiGen AI Design MCP?

MeiGen AI Design MCP scores 54.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.8k GitHub stars and is categorized under MCP Servers.

MeiGen AI Design MCP

jau123/MeiGen-AI-Design-MCP

Supports GPT Image 2, Seedance & ComfyUI, with a 1,400+ prompt library, carefully crafted hooks and a multi-task orchestration system

MCP Servers TypeScript Listed MIT

Is MeiGen AI Design MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 0%

Last push yesterday

Compare MeiGen AI Design MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MeiGen AI Design MCP scores 54.9/100 (Grade C), ranked #789 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.1/10; recent commits are unsigned; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How MeiGen AI Design MCP compares in MCP Servers

#435 MCP NixOS 55.0 +0.1
#436 Miro 54.9 ±0
#437 MeiGen AI Design MCP 54.9 this agent
#438 Pagerduty MCP Server 54.8 −0.1
#439 Paper Distill MCP 54.8 −0.1

Bars show each HVTrust score; the tick marks MeiGen AI Design MCP’s 54.9.

Where the 54.9 comes from

HVTrust dimensions vs the MCP Servers average

54.9 / 100 · 100.0% confidence

MeiGen AI Design MCP MCP Servers average (775 agents)

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

3.9 / 25

6.4 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.3 / 20

1.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

11.6 / 20

4.4 above avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for MeiGen AI Design MCP View MCP Servers Report missing data

64.1

Activity sub-score · out of 100

#437

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 C 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-08-11 2026-09-26

Activity & Reach

Stars

1.8k

Forks

234

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

755

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #792

Analysis

Activity Inputs

64.1 / 100

StarsRepository reach

19.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

11.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 9, 2026 (refresh pending)

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MeiGen AI Design MCP

Public trust evidence for MeiGen AI Design MCP 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 MeiGen AI Design MCP publish package provenance?

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

Does MeiGen AI Design MCP have an OpenSSF Scorecard?

MeiGen AI Design MCP has an OpenSSF Scorecard score of 3.1/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 MeiGen AI Design MCP actively maintained?

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

What license does MeiGen AI Design MCP use?

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

Are MeiGen AI Design MCP's commits signed?

0% of the last 100 commits to MeiGen AI Design MCP 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

MeiGen AI Design MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 MeiGen AI Design MCP'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

Maintain MeiGen AI Design MCP?

For maintainers

HVTrust scores MeiGen AI Design MCP 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-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 124 spots (#922 → #798)

2026-09-23

HVTrust Changed

HVTrust up 28.2pts (26.4 → 54.6)

2026-09-22

Newly Listed

First tracked at rank #922

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank dropped 50 spots (#747 → #797)

2026-09-15

Rank Moved

Rank rose 160 spots (#907 → #747)

2026-09-15

HVTrust Changed

HVTrust up 5.1pts (50.6 → 55.7)

2026-09-15

Activity Score Changed

Activity score up 13pts (50 → 63)

2026-09-11

Rank Moved

Rank dropped 13 spots (#896 → #909)

2026-09-09

Rank Moved

Rank dropped 15 spots (#880 → #895)

2026-09-08

Rank Moved

Rank dropped 10 spots (#870 → #880)

2026-09-07

Rank Moved

Rank dropped 65 spots (#805 → #870)

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 380 spots (#1178 → #798)

2026-09-05

HVTrust Changed

HVTrust up 18.2pts (33.3 → 51.5)

2026-09-04

Rank Moved

Rank dropped 77 spots (#1101 → #1178)

2026-09-04

HVTrust Changed

HVTrust down 3.2pts (36.5 → 33.3)

2026-09-04

Activity Score Changed

Activity score down 15pts (66 → 51)

2026-09-03

Rank Moved

Rank dropped 48 spots (#1053 → #1101)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-09-02

Grade Changed

Trust grade C → D

2026-09-02

Rank Moved

Rank dropped 529 spots (#524 → #1053)

2026-09-02

HVTrust Changed

HVTrust down 19.3pts (55.8 → 36.5)

2026-09-01

Rank Moved

Rank dropped 12 spots (#512 → #524)

2026-08-31

Scorecard Added

OSSF Scorecard: 3.1/10

2026-08-31

Grade Changed

Trust grade D → C

2026-08-31

Rank Moved

Rank rose 482 spots (#994 → #512)

2026-08-31

HVTrust Changed

HVTrust up 21.8pts (34.1 → 55.9)

2026-08-30

Rank Moved

Rank dropped 51 spots (#943 → #994)

2026-08-29

Rank Moved

Rank dropped 52 spots (#891 → #943)

2026-08-28

Rank Moved

Rank dropped 32 spots (#859 → #891)

2026-08-27

Rank Moved

Rank dropped 22 spots (#837 → #859)

2026-08-26

Rank Moved

Rank dropped 107 spots (#730 → #837)

2026-08-16

Rank Moved

Rank dropped 14 spots (#707 → #721)

2026-08-10

Newly Listed

First tracked at rank #698

GitHub → npm: meigen

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/meigen-ai-design-mcp.svg)](https://hvtracker.net/agents/meigen-ai-design-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/meigen-ai-design-mcp"><img src="https://hvtracker.net/badge/meigen-ai-design-mcp.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.3 · Raw JSON