Is MeiGen AI Design MCP safe to use?

MeiGen AI Design MCP has an HVTrust score of 57.5/100 (Grade C), ranked #778 of 1374 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 57.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.8k GitHub stars and is categorized under MCP Servers.

MeiGen AI Design MCP

Repository

Website

Discover inspiration and create images and videos with the latest AI models. Works with ChatGPT, Claude, Cursor, and other MCP clients.

MCP Servers TypeScript Listed MIT

Is MeiGen AI Design MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 2%

Last push 4d ago

Advisories None known

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 57.5/100 (Grade C), ranked #778 of 1374 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; 2% of recent commits are signed; no published advisory affects its latest release (meigen); last pushed 2026-11-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How MeiGen AI Design MCP 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.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 72.2 B · #194 of 778
Raise the OSSF Scorecard from 3.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.3 → 69.8 B · #226 of 778
Sign every commit2% signed today +4.9 → 62.4 C · #349 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MeiGen AI Design MCP 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 Partly signed

github.com/jau123/MeiGen-AI-Design-MCP, MIT, last pushed 2026-11-06. 2% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

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

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
Published packages Linked, not attested
- npm meigen Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: meigen 3.4.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-08-31 OSSF Scorecard: 3.1/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 MeiGen AI Design MCP’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 MeiGen AI Design MCP compares in MCP Servers

#419 MCP Console Automation 57.5 ±0
#420 Cr7258 Elasticsearch MCP Server 57.5 ±0
#421 MeiGen AI Design MCP 57.5 this agent
#422 Buildkite MCP Server 57.4 −0.1
#423 ArcGIS MCP Bridge 57.4 −0.1

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

Where the 57.5 comes from

HVTrust dimensions vs the MCP Servers average

57.5 / 100 · 100.0% confidence

MeiGen AI Design MCP MCP Servers average (778 agents)

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

4.0 / 25

6.8 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.2 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

17.4 / 20

5.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

11.5 / 20

3.9 above avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-09

Rank Moved

Rank dropped 17 spots (#762 → #779)

2026-11-08

Rank Moved

Rank rose 11 spots (#773 → #762)

2026-11-07

Rank Moved

Rank dropped 18 spots (#755 → #773)

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 View MCP Servers Report missing data

72.7

Activity sub-score · out of 100

#421

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-09-29 2026-11-10

Activity & Reach

Stars

1.8k

Forks

236

Last Push

2026-11-06

4 days ago

Commits (4 wk)

Downloads (7d)

536

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #779

Analysis

Activity Inputs

72.7 / 100

StarsRepository reach

19.5 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

17.6 / 25

CommunityFork signal

11.0 / 20

Common questions about MeiGen AI Design MCP

MeiGen AI Design MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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 4 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?

2% 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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-10-11

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-10-11

Mcp Status Changed

Detected MCP server support changed: implemented → declared

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-11-09

Rank Moved

Rank dropped 17 spots (#762 → #779)

2026-11-08

Rank Moved

Rank rose 11 spots (#773 → #762)

2026-11-07

Rank Moved

Rank dropped 18 spots (#755 → #773)

2026-11-05

Rank Moved

Rank rose 13 spots (#770 → #757)

2026-11-01

Rank Moved

Rank rose 25 spots (#789 → #764)

2026-10-27

Rank Moved

Rank dropped 10 spots (#769 → #779)

2026-10-26

Rank Moved

Rank dropped 18 spots (#751 → #769)

2026-10-25

Rank Moved

Rank dropped 11 spots (#740 → #751)

2026-10-19

Rank Moved

Rank rose 16 spots (#751 → #735)

2026-10-14

Rank Moved

Rank rose 20 spots (#754 → #734)

2026-10-12

Rank Moved

Rank rose 10 spots (#755 → #745)

2026-10-11

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-10-11

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-10-11

Rank Moved

Rank dropped 58 spots (#697 → #755)

2026-10-10

Rank Moved

Rank rose 50 spots (#747 → #697)

2026-10-09

Rank Moved

Rank dropped 11 spots (#736 → #747)

2026-09-27

Rank Moved

Rank rose 63 spots (#760 → #697)

2026-09-26

Rank Moved

Rank rose 32 spots (#792 → #760)

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)

GitHub → Website → 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.4 · Raw JSON

MeiGen AI Design MCP

How MeiGen AI Design MCP could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages Linked, not 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 MeiGen AI Design MCP compares in MCP Servers

Where the 57.5 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MeiGen AI Design MCP

AI agent surface

Maintain MeiGen AI Design MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers