Is Vidlens MCP safe to use?

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

What is the trust score for Vidlens MCP?

Vidlens MCP scores 45.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 35 GitHub stars and is categorized under MCP Servers.

Vidlens MCP

thatsrajan/vidlens-mcp

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.2 / 10

Provenance None

Signed commits 0%

Last push 35d ago

Compare Vidlens MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Vidlens MCP scores 45.9/100 (Grade D), ranked #1041 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 3.2/10; recent commits are unsigned; last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Vidlens MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Vidlens MCP’s 45.9.

Where the 45.9 comes from

HVTrust dimensions vs the MCP Servers average

45.9 / 100 · 100.0% confidence

Vidlens MCP MCP Servers average (775 agents)

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

4.0 / 25

6.3 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.2 / 17

1.0 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.7 / 20

2.4 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.3 / 20

0.9 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 (#1031 → #1041)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependencies: Google Gemini, OpenAI

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.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 35 days ago. Fresh activity helps separate stable projects from stale ones.

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

33.0

Activity sub-score · out of 100

#610

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

Forks

Last Push

2026-08-22

35 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #1041

Analysis

Activity Inputs

33.0 / 100

StarsRepository reach

9.3 / 30

FreshnessLast push recency

20.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Vidlens MCP

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

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

Does Vidlens MCP have an OpenSSF Scorecard?

Vidlens MCP has an OpenSSF Scorecard score of 3.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 Vidlens MCP actively maintained?

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

What license does Vidlens MCP use?

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

Are Vidlens MCP's commits signed?

0% of the last 100 commits to Vidlens 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

Vidlens MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

shell

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 Vidlens 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-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependencies: Google Gemini, OpenAI

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Vidlens MCP?

For maintainers

HVTrust scores Vidlens 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 10 spots (#1031 → #1041)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependencies: Google Gemini, OpenAI

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 125 spots (#1148 → #1023)

2026-09-23

HVTrust Changed

HVTrust up 25.5pts (20.7 → 46.2)

2026-09-22

Newly Listed

First tracked at rank #1148

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade C → D

2026-09-19

Rank Moved

Rank dropped 38 spots (#914 → #952)

2026-09-19

Activity Score Changed

Activity score down 6pts (47 → 42)

2026-09-15

Rank Moved

Rank dropped 10 spots (#896 → #906)

2026-09-12

Rank Moved

Rank dropped 12 spots (#892 → #904)

2026-09-11

Rank Moved

Rank dropped 13 spots (#879 → #892)

2026-09-09

Rank Moved

Rank dropped 19 spots (#854 → #873)

2026-09-08

Rank Moved

Rank dropped 13 spots (#841 → #854)

2026-09-07

Rank Moved

Rank dropped 60 spots (#781 → #841)

2026-09-06

Rank Moved

Rank dropped 10 spots (#771 → #781)

2026-09-05

Rank Moved

Rank dropped 70 spots (#701 → #771)

2026-09-04

Rank Moved

Rank dropped 25 spots (#676 → #701)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 429 spots (#1105 → #676)

2026-09-03

HVTrust Changed

HVTrust up 18.5pts (34.3 → 52.8)

2026-09-02

Scorecard Added

OSSF Scorecard: 3.2/10

2026-09-02

Rank Moved

Rank rose 158 spots (#1263 → #1105)

2026-09-02

HVTrust Changed

HVTrust up 14.8pts (19.5 → 34.3)

2026-09-01

Rank Moved

Rank dropped 16 spots (#1247 → #1263)

2026-08-31

Rank Moved

Rank dropped 17 spots (#1230 → #1247)

2026-08-30

Rank Moved

Rank dropped 19 spots (#1211 → #1230)

2026-08-29

Rank Moved

Rank dropped 19 spots (#1192 → #1211)

2026-08-28

Rank Moved

Rank dropped 18 spots (#1174 → #1192)

2026-08-27

Rank Moved

Rank dropped 14 spots (#1160 → #1174)

2026-08-26

Rank Moved

Rank dropped 55 spots (#1105 → #1160)

2026-08-24

Rank Moved

Rank dropped 11 spots (#1091 → #1102)

2026-08-22

Rank Moved

Rank rose 16 spots (#1112 → #1096)

2026-08-20

Rank Moved

Rank rose 25 spots (#1142 → #1117)

2026-08-20

Activity Score Changed

Activity score up 6pts (45 → 51)

2026-08-19

Rank Moved

Rank rose 46 spots (#1188 → #1142)

2026-08-19

Activity Score Changed

Activity score up 8pts (37 → 45)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1169 → #1194)

2026-08-10

Rank Moved

Rank dropped 72 spots (#1115 → #1187)

2026-08-08

Newly Listed

First tracked at rank #1110

GitHub → npm: vidlens-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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