Icon Composer MCP

Apple Icon Composer CLI & MCP server: create and manipulate .icon bundles and images with Liquid Glass rendering

MCP Servers TypeScript Listed MIT

Is Icon Composer MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.6 / 10
Provenance Attested
Signed commits 50%
Last push 174d ago
Compare Icon Composer MCP
Suggest a correction

In detail: Icon Composer MCP scores 57.4/100 (Grade C), ranked #711 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.6/10; 50% of recent commits are signed; last pushed 2026-04-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Icon Composer MCP compares in MCP Servers

  1. #391 Rust MCP Sdk 57.5 +0.1
  2. #392 Logic Pro MCP 57.5 +0.1
  3. #393 Icon Composer MCP 57.4 this agent
  4. #394 Runapi Ai MCP 57.3 −0.1
  5. #395 MCP Youtube Transcript 57.3 −0.1

Bars show each HVTrust score; the tick marks Icon Composer MCP’s 57.4.

Where the 57.4 comes from

HVTrust dimensions vs the MCP Servers average

57.4 / 100 · 100.0% confidence

Icon Composer MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.5 / 25
4.2 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
0.6 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0.4 / 20
11.6 below avg 12.0
AdoptionLog-scaled stars · package downloads
6.9 / 20
in line with avg 7.3

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 174 days ago. Fresh activity helps separate stable projects from stale ones.
13.6
Activity sub-score · out of 100
#393

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 →

Signals refreshed 2026-09-27 06:32 UTC · Repo last pushed 174 days ago

Rank Trend

2026-08-11 2026-09-27

Activity & Reach

Stars
53
Forks
2
Last Push
2026-04-06
174 days ago
Commits (4 wk)
0
Downloads (7d)
109
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼4
was #707

Analysis

Activity Inputs

13.6 / 100
StarsRepository reach
10.4 / 30
FreshnessLast push recency
0.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.6 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
50%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Icon Composer MCP

Icon Composer 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 Icon Composer MCP publish package provenance?
Yes. Icon Composer MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Icon Composer MCP have an OpenSSF Scorecard?
Icon Composer MCP has an OpenSSF Scorecard score of 3.6/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 Icon Composer MCP actively maintained?
Slowing down. Last push was 174 days ago — keep an eye on whether activity resumes.
What license does Icon Composer MCP use?
Icon Composer MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Icon Composer MCP's commits signed?
50% of the last 100 commits to Icon Composer 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
Icon Composer MCP 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
None detected
No clear plugin system or broad tool 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 Icon Composer 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
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Icon Composer MCP?

For maintainers

HVTrust scores Icon Composer 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.

Reputation Timeline

Signal history
Rank 18HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 556 spots (#1251 → #695)
2026-09-23
HVTrust Changed
HVTrust up 42.1pts (15.5 → 57.6)
2026-09-22
Newly Listed
First tracked at rank #1251
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 12 spots (#650 → #662)
2026-09-11
Rank Moved
Rank dropped 16 spots (#634 → #650)
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 510 spots (#1123 → #613)
2026-09-07
HVTrust Changed
HVTrust up 19.5pts (39.3 → 58.8)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1109 → #1123)
2026-09-05
Rank Moved
Rank dropped 38 spots (#1071 → #1109)
2026-09-04
Rank Moved
Rank dropped 26 spots (#1045 → #1071)
2026-09-03
Rank Moved
Rank dropped 56 spots (#989 → #1045)
2026-09-02
Rank Moved
Rank dropped 44 spots (#945 → #989)
2026-09-01
Rank Moved
Rank dropped 40 spots (#905 → #945)
2026-08-31
Rank Moved
Rank dropped 32 spots (#873 → #905)
2026-08-30
Rank Moved
Rank dropped 35 spots (#838 → #873)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.6/10
2026-08-29
Rank Moved
Rank rose 45 spots (#883 → #838)
2026-08-29
HVTrust Changed
HVTrust up 5.0pts (34.5 → 39.5)
2026-08-28
Rank Moved
Rank dropped 30 spots (#853 → #883)
2026-08-27
Rank Moved
Rank dropped 23 spots (#830 → #853)
2026-08-26
Rank Moved
Rank dropped 107 spots (#723 → #830)
2026-08-16
Rank Moved
Rank dropped 17 spots (#699 → #716)
2026-08-10
Rank Moved
Rank dropped 34 spots (#663 → #697)
2026-08-08
Newly Listed
First tracked at rank #666

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/icon-composer-mcp.svg)](https://hvtracker.net/agents/icon-composer-mcp)
HTML:
<a href="https://hvtracker.net/agents/icon-composer-mcp"><img src="https://hvtracker.net/badge/icon-composer-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