Lighthouse (l3wi) MCP Server

mcp-lighthouse npm v0.1.4

Published by l3wi — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

An MCP server for Lighthouse.one portfolio tracker.

View on npm ↗ Repository ↗ Raw report (JSON) ↗

Trust grade

96/100

Last scanned 2026-09-07 get badge →

Trust

A · 96/100

Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.

Capability

Moderate

Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.

Coverage

Source

How much the scan could actually inspect. Shallow coverage is stated, never hidden.

A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

Points	Adoption-risk factor
−3	capability blast radius (moderate) — client exposure if the model is manipulated
−1	publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Hardcoded egress to an external endpoint (dist/lighthouse.js)MTC-SRC-003

In the server's implementation (`dist/lighthouse.js:102`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch("https://lighthouse.one/v1/login", { method: "POST", heade

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/lighthouse.js

Tools 5

Each tool and what it can reach — statically extracted from the published source.

authenticateno sensitive capability
getLighthousePerformanceDatano sensitive capability
getLighthousePortfoliono sensitive capability
getLighthouseYieldDatano sensitive capability
listLighthousePortfoliosno sensitive capability

What this scan could not see

Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

Version	Score	Findings	Engine	Scanned
`v0.1.4` latest	A 96/100	1	1.13.0	2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

Markdown (GitHub README)

[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-lighthouse/badge.svg)](https://mcptrustchecker.com/registry/mcp-lighthouse)

HTML

<a href="https://mcptrustchecker.com/registry/mcp-lighthouse"><img src="https://mcptrustchecker.com/registry/mcp-lighthouse/badge.svg" alt="MCP Trust Score" height="20"></a>

Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-lighthouse/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-lighthouse --online

Use the free API → How scoring works

Other implementations of Lighthouse 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

Lighthouse (danielsogl) Source verified npm

@danielsogl/lighthouse-mcp

A comprehensive Model Context Protocol (MCP) server that provides web performance auditing, accessibility testing, SEO analysis, security assessment, and Core Web Vitals monitoring using Google Lighthouse. Enables LLMs and AI agents to perform detailed we

Security & Testing Score 100/100 0 findings 1.2k/wk Cap. Minimal

Lighthouse (fullstackdegen) npm

mcp-server-lighthouse

Turn mobile and desktop Lighthouse audits into evidence-backed coding-agent tasks.

Developer Tools Score 99/100 0 findings 14/wk Cap. Minimal

Lighthouse (npm) npm

lighthouse-mcp

MCP server for Google Lighthouse performance metrics

Analytics & Monitoring Score 98/100 0 findings 1.4k/wk Cap. Minimal

Lighthouse (npm) npm

lighthouse-mcp-server

MCP server for using the Lighthouse AI API