MCP Image
MCP server for AI image generation and editing with automatic prompt optimization and quality presets. Supports Nano Banana (Gemini), OpenAI GPT Image, and BytePlus Seedream.
Is MCP Image safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Image
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Image scores 64.5/100 (Grade C), ranked #486 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 5.7/10; 39% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Image compares in MCP Servers
- #278 Korean Law MCP 64.7 +0.2
- #279 NetLogo MCP 64.6 +0.1
- #280 MCP Image 64.5 this agent
- #281 Mapbox MCP Server 64.5 ±0
- #282 Claude Faf MCP 64.5 ±0
Bars show each HVTrust score; the tick marks MCP Image’s 64.5.
Where the 64.5 comes from
HVTrust dimensions vs the MCP Servers average
64.5 / 100 · 100.0% confidenceMCP Image MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
62.2 / 100Supply Chain Trust
Common questions about MCP Image
Does MCP Image publish package provenance?
Does MCP Image have an OpenSSF Scorecard?
Is MCP Image actively maintained?
What license does MCP Image use?
Are MCP Image's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Image'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.
Maintain MCP Image?
For maintainers
HVTrust scores MCP Image 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-image)
<a href="https://hvtracker.net/agents/mcp-image"><img src="https://hvtracker.net/badge/mcp-image.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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