Is Lighthouse MCP safe to use?

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

What is the trust score for Lighthouse MCP?

Lighthouse MCP scores 58.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 209 GitHub stars and is categorized under MCP Servers.

Lighthouse MCP

priyankark/lighthouse-mcp

Allows AI assistants such as Amp/Cline/Cursor/Claude Code/Codex/GitHub Copilot to use Google's lighthouse tool to measure perf metrics for your webpage. You can then run an agentic loop and get the assistants to optimize those metrics!

MCP Servers TypeScript Listed MIT

Is Lighthouse MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10

Provenance None

Signed commits 43%

Last push 13d ago

Compare Lighthouse MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Lighthouse MCP scores 58.8/100 (Grade C), ranked #668 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.7/10; 43% of recent commits are signed; last pushed 2026-09-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Lighthouse MCP compares in MCP Servers

#368 E Arveldaja MCP 58.9 +0.1
#369 MCP Abap Adt 58.9 +0.1
#370 Lighthouse MCP 58.8 this agent
#371 Cisco Modeling Labs CML 58.7 −0.1
#372 DMontgomery40 DeepSeek MCP Server 58.6 −0.2

Bars show each HVTrust score; the tick marks Lighthouse MCP’s 58.8.

Where the 58.8 comes from

HVTrust dimensions vs the MCP Servers average

58.8 / 100 · 100.0% confidence

Lighthouse MCP 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.6 / 17

0.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.9 / 20

1.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

9.7 / 20

2.5 above 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-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 rose 315 spots (#969 → #654)

Maintainer Checklist

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

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

52.0

Activity sub-score · out of 100

#370

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 C 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

209

Forks

Last Push

2026-09-13

13 days ago

Commits (4 wk)

Downloads (7d)

1,168

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼9

was #659

Analysis

Activity Inputs

52.0 / 100

StarsRepository reach

13.9 / 30

FreshnessLast push recency

23.2 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

6.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 21, 2026

Signed Commits

43%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow -1

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 3

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 10

Common questions about Lighthouse MCP

Lighthouse MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Lighthouse MCP publish package provenance?

No published build provenance is currently detected for Lighthouse 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 Lighthouse MCP have an OpenSSF Scorecard?

Lighthouse MCP has an OpenSSF Scorecard score of 3.7/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 Lighthouse MCP actively maintained?

Maintained. Last push was 13 days ago.

What license does Lighthouse MCP use?

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

Are Lighthouse MCP's commits signed?

42% of the last 100 commits to Lighthouse 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

Lighthouse MCP 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

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 Lighthouse 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-07

Activity Resumed

Activity resumed

2026-08-21

Activity Went Stale

No commits for 90 days

Maintain Lighthouse MCP?

For maintainers

HVTrust scores Lighthouse 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-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 rose 315 spots (#969 → #654)

2026-09-23

HVTrust Changed

HVTrust up 33.6pts (25.5 → 59.1)

2026-09-22

Newly Listed

First tracked at rank #969

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank rose 13 spots (#685 → #672)

2026-09-14

Rank Moved

Rank dropped 11 spots (#664 → #675)

2026-09-13

Rank Moved

Rank rose 111 spots (#775 → #664)

2026-09-13

HVTrust Changed

HVTrust up 3.3pts (55.0 → 58.3)

2026-09-09

Rank Moved

Rank dropped 15 spots (#747 → #762)

2026-09-07

Activity Resumed

Activity resumed

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 286 spots (#1024 → #738)

2026-09-07

HVTrust Changed

HVTrust up 11.7pts (43.6 → 55.3)

2026-09-07

Activity Score Changed

Activity score up 21pts (30 → 51)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1008 → #1024)

2026-09-05

Rank Moved

Rank dropped 48 spots (#960 → #1008)

2026-09-04

Rank Moved

Rank dropped 26 spots (#934 → #960)

2026-09-03

Rank Moved

Rank rose 258 spots (#1192 → #934)

2026-09-03

HVTrust Changed

HVTrust up 16.7pts (27.1 → 43.8)

2026-09-02

Rank Moved

Rank dropped 38 spots (#1154 → #1192)

2026-09-01

Rank Moved

Rank dropped 41 spots (#1113 → #1154)

2026-08-31

Rank Moved

Rank dropped 32 spots (#1081 → #1113)

2026-08-30

Rank Moved

Rank dropped 48 spots (#1033 → #1081)

2026-08-29

Rank Moved

Rank dropped 51 spots (#982 → #1033)

2026-08-28

Rank Moved

Rank dropped 36 spots (#946 → #982)

2026-08-27

Scorecard Added

OSSF Scorecard: 2.7/10

2026-08-27

Rank Moved

Rank rose 337 spots (#1283 → #946)

2026-08-27

HVTrust Changed

HVTrust up 12.4pts (15.0 → 27.4)

2026-08-26

Rank Moved

Rank dropped 19 spots (#1264 → #1283)

2026-08-21

Activity Went Stale

No commits for 90 days

2026-08-16

Rank Moved

Rank dropped 28 spots (#1236 → #1264)

2026-08-10

Rank Moved

Rank dropped 76 spots (#1157 → #1233)

2026-08-08

Newly Listed

First tracked at rank #1155

GitHub → npm: lighthouse-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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