updated 2026-10-16 20:06 UTC

Lighthouse MCP

Repository

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.4 / 10
Provenance None
Signed commits 43%
Last push today
Advisories None known
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 56.3/100 (Grade C), ranked #797 of 1378 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.4/10; 43% of recent commits are signed; no published advisory affects its latest release (lighthouse-mcp); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Lighthouse MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Lighthouse MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/priyankark/lighthouse-mcp, MIT, last pushed 2026-10-16. 43% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.4/10 (scanned Oct 5, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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 7

  3. Published packages Linked, not attested

    • npm lighthouse-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: lighthouse-mcp 0.1.17. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 2.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Lighthouse MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Lighthouse MCP compares in MCP Servers

  1. #428 Bgg MCP 56.4 +0.1
  2. #429 Kibana 56.3 ±0
  3. #430 Lighthouse MCP 56.3 this agent
  4. #431 Awesome Copilot MCP Server 56.2 −0.1
  5. #432 SAS MCP Server 56.2 −0.1

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

Where the 56.3 comes from

HVTrust dimensions vs the MCP Servers average

56.3 / 100 · 100.0% confidence

Lighthouse MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.4 / 25
4.1 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.9 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.0 / 20
in line with avg 12.3
AdoptionLog-scaled stars · package downloads
9.7 / 20
2.3 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 10 spots (#789 → #799)
2026-10-14
Rank Moved
Rank dropped 25 spots (#764 → #789)
2026-10-14
Activity Score Changed
Activity score down 5pts (50 → 45)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
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
45.2
Activity sub-score · out of 100
#430
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 →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
211
Forks
21
Last Push
2026-10-16
today
Commits (4 wk)
0?
Downloads (7d)
1,288
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #799

Analysis

Activity Inputs

45.2 / 100
StarsRepository reach
14.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.2 / 20

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.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 Lighthouse MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
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
Rank 25HVTrust 5Listed 2Score 2Grade 2Stale 1Scorecard 1Fresh 1Delisted 1MCP 1
2026-10-15
Rank Moved
Rank dropped 10 spots (#789 → #799)
2026-10-14
Rank Moved
Rank dropped 25 spots (#764 → #789)
2026-10-14
Activity Score Changed
Activity score down 5pts (50 → 45)
2026-10-13
Rank Moved
Rank dropped 10 spots (#754 → #764)
2026-10-07
Rank Moved
Rank dropped 18 spots (#716 → #734)
2026-10-05
Rank Moved
Rank dropped 22 spots (#694 → #716)
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
HVTrust 56.3 Grade C
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.4 · Raw JSON