Glidermcp Com

Glider MCP - code analysis for AI assistants

MCP Servers Listed MIT

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

OSSF Scorecard 4.0 / 10
Provenance None
Signed commits 36%
Last push 14d ago
Compare Glidermcp Com
Suggest a correction

In detail: Glidermcp Com scores 45.2/100 (Grade D), ranked #1061 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 4.0/10; 36% of recent commits are signed; last pushed 2026-09-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Glidermcp Com compares in MCP Servers

  1. #621 Google Knowledge Graph MCP 45.3 +0.1
  2. #622 Storeshots MCP 45.3 +0.1
  3. #623 Glidermcp Com 45.2 this agent
  4. #624 Pty MCP 45.1 −0.1
  5. #625 CodeWiki MCP — AI-generated docs for GitHub repos 45.1 −0.1

Bars show each HVTrust score; the tick marks Glidermcp Com’s 45.2.

Where the 45.2 comes from

HVTrust dimensions vs the MCP Servers average

45.2 / 100 · 100.0% confidence

Glidermcp Com MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
3.5 below 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
11.9 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.0 / 20
0.9 above avg 12.1
AdoptionLog-scaled stars · package downloads
3.0 / 20
4.2 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 (#1051 → #1061)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
38.0
Activity sub-score · out of 100
#623

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 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 14 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
16
Forks
1
Last Push
2026-09-12
14 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
5
Rank Change
=
was #1061

Analysis

Activity Inputs

38.0 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

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

Common questions about Glidermcp Com

Public trust evidence for Glidermcp Com 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 Glidermcp Com publish package provenance?
No published build provenance is currently detected for Glidermcp Com. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Glidermcp Com have an OpenSSF Scorecard?
Glidermcp Com has an OpenSSF Scorecard score of 4.0/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 Glidermcp Com actively maintained?
Maintained. Last push was 14 days ago.
What license does Glidermcp Com use?
Glidermcp Com ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Glidermcp Com's commits signed?
36% of the last 100 commits to Glidermcp Com 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 Glidermcp Com'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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-13
Mcp Status Changed
Detected MCP server support changed: implemented → none

Maintain Glidermcp Com?

For maintainers

HVTrust scores Glidermcp Com 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 25Score 3HVTrust 3Listed 2Scorecard 1MCP 1Delisted 1Surface 1Surface 1
2026-09-25
Rank Moved
Rank dropped 10 spots (#1051 → #1061)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Rank Moved
Rank dropped 471 spots (#575 → #1046)
2026-09-23
HVTrust Changed
HVTrust up 10.0pts (35.4 → 45.4)
2026-09-22
Newly Listed
First tracked at rank #575
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank rose 18 spots (#1060 → #1042)
2026-09-13
Mcp Status Changed
Detected MCP server support changed: implemented → none
2026-09-13
Rank Moved
Rank dropped 50 spots (#1000 → #1050)
2026-09-12
Rank Moved
Rank rose 17 spots (#1017 → #1000)
2026-09-12
Activity Score Changed
Activity score up 6pts (34 → 40)
2026-09-11
Rank Moved
Rank rose 69 spots (#1086 → #1017)
2026-09-11
HVTrust Changed
HVTrust up 3.0pts (43.2 → 46.2)
2026-09-11
Activity Score Changed
Activity score up 6pts (28 → 34)
2026-09-09
Rank Moved
Rank dropped 12 spots (#1072 → #1084)
2026-09-07
Rank Moved
Rank dropped 37 spots (#1026 → #1063)
2026-09-06
Rank Moved
Rank dropped 11 spots (#1015 → #1026)
2026-09-05
Rank Moved
Rank dropped 46 spots (#969 → #1015)
2026-09-04
Rank Moved
Rank dropped 31 spots (#938 → #969)
2026-09-03
Rank Moved
Rank dropped 54 spots (#884 → #938)
2026-09-02
Rank Moved
Rank dropped 47 spots (#837 → #884)
2026-09-01
Rank Moved
Rank dropped 34 spots (#803 → #837)
2026-08-31
Rank Moved
Rank dropped 33 spots (#770 → #803)
2026-08-30
Rank Moved
Rank dropped 28 spots (#742 → #770)
2026-08-29
Rank Moved
Rank dropped 47 spots (#695 → #742)
2026-08-28
Rank Moved
Rank dropped 24 spots (#671 → #695)
2026-08-27
Rank Moved
Rank dropped 19 spots (#652 → #671)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.0/10
2026-08-26
Rank Moved
Rank rose 408 spots (#1060 → #652)
2026-08-26
HVTrust Changed
HVTrust up 23.9pts (20.3 → 44.2)
2026-08-26
Activity Score Changed
Activity score down 10pts (40 → 30)
2026-08-24
Rank Moved
Rank dropped 28 spots (#1032 → #1060)
2026-08-17
Rank Moved
Rank rose 13 spots (#1033 → #1020)
2026-08-16
Rank Moved
Rank dropped 30 spots (#1003 → #1033)
2026-08-12
Rank Moved
Rank rose 13 spots (#1003 → #990)
2026-08-10
Rank Moved
Rank dropped 57 spots (#944 → #1001)
2026-08-08
Newly Listed
First tracked at rank #932

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 45.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/glidermcp-com.svg)](https://hvtracker.net/agents/glidermcp-com)
HTML:
<a href="https://hvtracker.net/agents/glidermcp-com"><img src="https://hvtracker.net/badge/glidermcp-com.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