lhci-server

lhci-server runs the server component of Lighthouse CI, providing an HTTP API/UI to receive upload results from Lighthouse CI runners, store them, and serve reports/insights and project history.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Monitoring ai-ml devtools infrastructure monitoring performance lighthouse ci-cd
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
48
/ 100
Is it safe for agents?
⚡ Reliability
38
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
40
Error Messages
0
Auth Simplicity
55
Rate Limits
10

🔒 Security

TLS Enforcement
60
Auth Strength
50
Scope Granularity
30
Dep. Hygiene
50
Secret Handling
50

Because exact server security configuration and dependency status are not provided in the prompt, scores are conservative. For self-hosted deployments, TLS termination and secret storage are strongly dependent on operator configuration (reverse proxy, environment variables, and least-privilege).

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
50
AF Security Reliability

Best When

You already use Lighthouse CI in CI pipelines and want centralized storage, history, and viewing via a server.

Avoid When

You need a fully hosted managed service without self-hosting or you require features unrelated to Lighthouse CI reporting/storage.

Use Cases

  • Centralize Lighthouse CI runs and history for multiple projects/branches
  • Automate collection of Lighthouse/CrUX-style performance metrics from CI
  • Provide a web interface/API for viewing Lighthouse reports and trends
  • Enable integrations that need a service endpoint to submit Lighthouse run data

Not For

  • A general-purpose crawling/performance testing service unrelated to Lighthouse CI workflows
  • A replacement for hosted commercial observability platforms without Lighthouse CI integration requirements

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: API token / server authentication (typical for LHCI server deployments)
OAuth: No Scopes: No

Auth mechanism and scope granularity are not verifiable from the provided prompt; LHCI server deployments commonly rely on bearer tokens or session auth, but exact details aren’t confirmed here.

Pricing

Free tier: No
Requires CC: No

Self-hosted open-source package; no pricing information is provided in the prompt.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Server behavior depends on configuration (storage backend, auth settings, upload endpoints); without exact API docs, agents may need to handle 4xx/5xx based on trial calls.
  • Uploads and report indexing may be asynchronous; agents should not assume immediate read-after-write unless documented.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for lhci-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered