Glif
Website
Glif's hosted MCP server, plugin and skills for creating images, video and audio. Works with Claude, ChatGPT, Codex, Cursor and more.
Is Glif safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Glif
How does it stack up against its MCP Servers neighbours?
- JADX MCP Server +0.2 higher
- WPFVisualTreeMcp +0.1 higher
- Microsoft MCP Server for Enterprise 0.1 lower
In detail: Glif scores 51.3/100 (Grade C), ranked #969 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 92% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Glif 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 5.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +8.1 → 59.4 C · #385 of 778
Chain of custody
Scanners check what the code says. This traces who ships Glif and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/glifxyz/glif-mcp-server, MIT, last pushed 2026-10-09. 92% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 2CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 3Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 9Vulnerabilities 10 -
Published packages None
No registry package. Glif is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-09-01 OSSF Scorecard: 5.4/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Glif’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 Glif compares in MCP Servers
- #541 JADX MCP Server 51.5 +0.2
- #542 WPFVisualTreeMcp 51.4 +0.1
- #543 Glif 51.3 this agent
- #544 Microsoft MCP Server for Enterprise 51.2 −0.1
- #545 GPU MCP Server 51.1 −0.2
Bars show each HVTrust score; the tick marks Glif’s 51.3.
Where the 51.3 comes from
HVTrust dimensions vs the MCP Servers average
51.3 / 100 · 100.0% confidenceGlif MCP Servers average (778 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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
41.8 / 100Common questions about Glif
Does Glif publish package provenance?
Does Glif have an OpenSSF Scorecard?
Is Glif actively maintained?
What license does Glif use?
Are Glif'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 Glif'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 Glif?
For maintainers
HVTrust scores Glif 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/glif)
<a href="https://hvtracker.net/agents/glif"><img src="https://hvtracker.net/badge/glif.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON