Is MCP Slim Guard safe to use?

MCP Slim Guard has an HVTrust score of 49.0/100 (Grade D), ranked #963 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Slim Guard?

MCP Slim Guard scores 49.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 188 GitHub stars and is categorized under MCP Servers.

MCP Slim Guard

lennney/mcp-slim-guard

Context compression for MCP. Same upstream call, exact results recoverable.

MCP Servers TypeScript Listed MIT

Is MCP Slim Guard safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 5%

Last push 43d ago

Compare MCP Slim Guard

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Slim Guard scores 49.0/100 (Grade D), ranked #963 of 1325 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 4.2/10; 5% of recent commits are signed; last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Slim Guard compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Slim Guard’s 49.0.

Where the 49.0 comes from

HVTrust dimensions vs the MCP Servers average

49.0 / 100 · 100.0% confidence

MCP Slim Guard MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.5 / 25

4.8 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

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.1 / 20

2.9 below avg 12.0

AdoptionLog-scaled stars · package downloads

7.5 / 20

in line with 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 12 spots (#949 → #961)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank rose 116 spots (#1063 → #947)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.2/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.

Refresh maintenance signals The repo was last pushed 43 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Slim Guard View MCP Servers Report missing data

32.7

Activity sub-score · out of 100

#557

In MCP Servers

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

2026-08-11 2026-09-26

Activity & Reach

Stars

188

Forks

Last Push

2026-08-14

43 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #961

Analysis

Activity Inputs

32.7 / 100

StarsRepository reach

13.7 / 30

FreshnessLast push recency

19.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

0.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Common questions about MCP Slim Guard

Public trust evidence for MCP Slim Guard 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 MCP Slim Guard publish package provenance?

No published build provenance is currently detected for MCP Slim Guard. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Slim Guard have an OpenSSF Scorecard?

MCP Slim Guard has an OpenSSF Scorecard score of 4.2/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 MCP Slim Guard actively maintained?

Slowing down. Last push was 43 days ago — keep an eye on whether activity resumes.

What license does MCP Slim Guard use?

MCP Slim Guard ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Slim Guard's commits signed?

5% of the last 100 commits to MCP Slim Guard 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

Declared

MCP support appears present, but direct server implementation is less certain.

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 MCP Slim Guard'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 → declared

2026-09-02

Mcp Status Changed

Detected MCP server support changed: implemented → declared

Maintain MCP Slim Guard?

For maintainers

HVTrust scores MCP Slim Guard 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 12 spots (#949 → #961)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank rose 116 spots (#1063 → #947)

2026-09-23

HVTrust Changed

HVTrust up 26.1pts (23.1 → 49.2)

2026-09-22

Newly Listed

First tracked at rank #1063

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-13

Grade Changed

Trust grade C → D

2026-09-13

Rank Moved

Rank dropped 24 spots (#906 → #930)

2026-09-11

Rank Moved

Rank dropped 24 spots (#877 → #901)

2026-09-09

Rank Moved

Rank dropped 18 spots (#860 → #878)

2026-09-08

Rank Moved

Rank dropped 32 spots (#828 → #860)

2026-09-07

Rank Moved

Rank dropped 60 spots (#768 → #828)

2026-09-05

Grade Changed

Trust grade D → C

2026-09-05

Rank Moved

Rank rose 385 spots (#1147 → #762)

2026-09-05

HVTrust Changed

HVTrust up 17.9pts (34.9 → 52.8)

2026-09-04

Rank Moved

Rank dropped 14 spots (#1133 → #1147)

2026-09-03

Rank Moved

Rank dropped 43 spots (#1090 → #1133)

2026-09-02

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-09-02

Rank Moved

Rank dropped 88 spots (#1002 → #1090)

2026-09-01

Rank Moved

Rank dropped 44 spots (#958 → #1002)

2026-08-31

Rank Moved

Rank dropped 44 spots (#914 → #958)

2026-08-30

Rank Moved

Rank dropped 71 spots (#843 → #914)

2026-08-30

Activity Score Changed

Activity score down 7pts (52 → 45)

2026-08-29

Rank Moved

Rank dropped 45 spots (#798 → #843)

2026-08-28

Rank Moved

Rank dropped 29 spots (#769 → #798)

2026-08-27

Rank Moved

Rank dropped 32 spots (#737 → #769)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.2/10

2026-08-26

Rank Moved

Rank rose 196 spots (#933 → #737)

2026-08-26

HVTrust Changed

HVTrust up 17.0pts (22.8 → 39.8)

2026-08-21

Rank Moved

Rank dropped 14 spots (#899 → #913)

2026-08-16

Rank Moved

Rank dropped 21 spots (#884 → #905)

2026-08-14

Rank Moved

Rank rose 12 spots (#899 → #887)

2026-08-12

Rank Moved

Rank rose 13 spots (#903 → #890)

2026-08-10

Rank Moved

Rank dropped 49 spots (#846 → #895)

2026-08-08

Newly Listed

First tracked at rank #843

GitHub → npm: mcp-slim-guard

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-slim-guard.svg)](https://hvtracker.net/agents/mcp-slim-guard)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-slim-guard"><img src="https://hvtracker.net/badge/mcp-slim-guard.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