MCP Drawthings
MCP server for Draw Things - local AI image generation on Mac
Is MCP Drawthings safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MCP Drawthings
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Drawthings scores 35.1/100 (Grade D), ranked #1295 of 1378 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 1.6/10; recent commits are unsigned; no published advisory affects its latest release (mcp-drawthings); last pushed 2026-01-01. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Drawthings 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 1.6 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +15.4 → 50.5 C · #559 of 781
- Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 49.8 D · #575 of 781
- Sign every commit0% signed today +5.0 → 40.1 D · #696 of 781
Chain of custody
Scanners check what the code says. This traces who ships MCP Drawthings 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 Unsigned
github.com/james-see/mcp-drawthings, MIT, last pushed 2026-01-01. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 1.6/10 (scanned Oct 12, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies -1SAST 0Security-Policy 0Signed-Releases -1Token-Permissions -1Vulnerabilities 0 -
Published packages Linked, not attested
- npm mcp-drawthings 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: mcp-drawthings 1.1.2. No published advisory affects it (OSV, checked 2026-10-17).
Changes to this chain
- 2026-08-26 OSSF Scorecard: 1.5/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 MCP Drawthings’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.
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 MCP Drawthings compares in MCP Servers
- #749 MCP Language Server 35.1 ±0
- #750 DevDocs 35.1 ±0
- #751 MCP Drawthings 35.1 this agent
- #752 Jotform MCP Server 34.5 −0.6
- #753 Yuvalsuede Memory MCP 34.5 −0.6
Bars show each HVTrust score; the tick marks MCP Drawthings’s 35.1.
Where the 35.1 comes from
HVTrust dimensions vs the MCP Servers average
35.1 / 100 · 100.0% confidenceMCP Drawthings MCP Servers average (781 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 D 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
12.1 / 100Common questions about MCP Drawthings
Does MCP Drawthings publish package provenance?
Does MCP Drawthings have an OpenSSF Scorecard?
Is MCP Drawthings actively maintained?
What license does MCP Drawthings use?
Are MCP Drawthings'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 Drawthings'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 Drawthings?
For maintainers
HVTrust scores MCP Drawthings 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-drawthings)
<a href="https://hvtracker.net/agents/mcp-drawthings"><img src="https://hvtracker.net/badge/mcp-drawthings.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.4 · Raw JSON