Glif

Deprecated — use the hosted Glif MCP server at https://glif.app/mcp

MCP Servers Listed MIT

Is Glif safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.4 / 10
Provenance None
Signed commits 94%
Last push 58d ago

In detail: Glif scores 51.0/100 (Grade C), ranked #911 of 1325 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.4/10; 94% of recent commits are signed; last pushed 2026-07-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How Glif compares in MCP Servers

  1. #516 Starwind UI MCP 51.3 +0.3
  2. #517 AEC Model Bridge 51.3 +0.3
  3. #518 Glif 51.0 this agent
  4. #519 Agent Memory MCP 51.0 ±0
  5. #520 SearXNG HTTP MCP 50.9 −0.1

Bars show each HVTrust score; the tick marks Glif’s 51.0.

Where the 51.0 comes from

HVTrust dimensions vs the MCP Servers average

51.0 / 100 · 100.0% confidence

Glif MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.4 / 25
1.1 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
0.9 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
8.1 / 20
4.0 below avg 12.1
AdoptionLog-scaled stars · package downloads
5.6 / 20
1.6 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 10 spots (#900 → #910)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/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.
Refresh maintenance signals The repo was last pushed 58 days ago. Fresh activity helps separate stable projects from stale ones.
38.1
Activity sub-score · out of 100
#518

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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 58 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
211
Forks
31
Last Push
2026-07-30
58 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▼1
was #910

Analysis

Activity Inputs

38.1 / 100
StarsRepository reach
14.0 / 30
FreshnessLast push recency
16.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.4 / 10
OpenSSF Scorecard · scanned Sep 18, 2026
Signed Commits
94%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 7
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 5
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 9
Vulnerabilities 10

Common questions about Glif

Public trust evidence for Glif is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Glif publish package provenance?
No published build provenance is currently detected for Glif. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Glif have an OpenSSF Scorecard?
Glif has an OpenSSF Scorecard score of 5.4/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 Glif actively maintained?
Slowing down. Last push was 58 days ago — keep an eye on whether activity resumes.
What license does Glif use?
Glif ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Glif's commits signed?
93% of the last 100 commits to Glif 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
Implemented
Glif 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
N/A
No package source configured
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 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.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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
Rank 23Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 10 spots (#900 → #910)
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 dropped 333 spots (#561 → #894)
2026-09-23
HVTrust Changed
HVTrust up 15.0pts (36.2 → 51.2)
2026-09-22
Newly Listed
First tracked at rank #561
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 15 spots (#846 → #861)
2026-09-09
Rank Moved
Rank dropped 15 spots (#831 → #846)
2026-09-07
Rank Moved
Rank dropped 39 spots (#785 → #824)
2026-09-06
Rank Moved
Rank dropped 10 spots (#775 → #785)
2026-09-05
Rank Moved
Rank dropped 63 spots (#712 → #775)
2026-09-04
Rank Moved
Rank dropped 26 spots (#686 → #712)
2026-09-03
Rank Moved
Rank dropped 40 spots (#646 → #686)
2026-09-02
Rank Moved
Rank dropped 32 spots (#614 → #646)
2026-09-01
Scorecard Added
OSSF Scorecard: 5.4/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 587 spots (#1201 → #614)
2026-09-01
HVTrust Changed
HVTrust up 30.9pts (21.7 → 52.6)
2026-08-31
Rank Moved
Rank dropped 23 spots (#1178 → #1201)
2026-08-30
Rank Moved
Rank dropped 56 spots (#1122 → #1178)
2026-08-29
Rank Moved
Rank dropped 36 spots (#1086 → #1122)
2026-08-28
Rank Moved
Rank dropped 29 spots (#1057 → #1086)
2026-08-27
Rank Moved
Rank dropped 20 spots (#1037 → #1057)
2026-08-26
Rank Moved
Rank dropped 87 spots (#950 → #1037)
2026-08-24
Rank Moved
Rank dropped 17 spots (#936 → #953)
2026-08-21
Rank Moved
Rank dropped 20 spots (#910 → #930)
2026-08-20
Rank Moved
Rank dropped 29 spots (#881 → #910)
2026-08-16
Rank Moved
Rank dropped 19 spots (#861 → #880)
2026-08-12
Rank Moved
Rank rose 11 spots (#864 → #853)
2026-08-10
Rank Moved
Rank dropped 47 spots (#809 → #856)
2026-08-08
Newly Listed
First tracked at rank #805

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 51.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/glif.svg)](https://hvtracker.net/agents/glif)
HTML:
<a href="https://hvtracker.net/agents/glif"><img src="https://hvtracker.net/badge/glif.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON