Open-source MCP server
Give Claude a speed lab for any website.
Lighthouse scores, Core Web Vitals, real-user field data and a ranked list of fixes — for your pages, a client's, or a competitor's — straight from a conversation. Read-only, public data only.
No Google sign-in: these APIs read public pages, so there is no account to authorise. Token creation is gated by a secret the server owner sets.
How it works
-
1
Create a token
Enter the access secret and a label. We mint a personal MCP bearer token for you — nothing else is stored.
-
2
Paste the install command
One
claude mcp addcommand, pre-filled with your token, ready to copy. Works in Claude Code, Claude Desktop, Cursor, Continue.dev — anything that speaks MCP. -
3
Ask about speed
Just ask. Examples:
- "Audit https://example.com on mobile — what are the top 3 fixes?"
- "Compare our pricing page with competitor.com/pricing."
- "Did last week's deploy make LCP worse for real users?"
4 tools, ready to call
audit_pageFull Lighthouse audit: scores, Core Web Vitals, ranked fixes with savings.
audit_pagesUp to 8 URLs in one call — compare pages or sweep a site.
real_user_vitalsReal Chrome-user Core Web Vitals (CrUX) — what Google ranks on.
vitals_trendWeekly real-user history, ~6 months — did that deploy help?
Security model
- • Google refresh tokens are encrypted with AES-256-GCM before being written to Mongo. Key lives in env, never in the database.
- • MCP bearer tokens are stored as sha256 hashes only — the plaintext is shown once on connect, then unrecoverable.
- • Per-request OAuth client is built from the decrypted refresh token, used for that single call, then discarded.
- • Revoke at any time — server-side revocation is instant.
- • Code is open-source on GitLab; self-host if you'd rather not trust a hosted service.