Measure Core Web Vitals and debug web performance with 56 snippets in a headless Chromium
MCPpedia last refreshed this data
io.github.nucliweb/webperf-snippets is an MCP server that measure Core Web Vitals and debug web performance with 56 snippets in a headless Chromium. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 64/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-nucliweb-webperf-snippets": {
"args": [
"-y",
"webperf-snippets"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Measure Core Web Vitals and debug web performance with 56 snippets in a headless Chromium
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked webperf-snippets against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in browser
Open-source web scraper for AI agents with scrape, crawl, and map tools
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
MCP Security Weekly
Get CVE alerts and security updates for io.github.nucliweb/webperf-snippets and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Tested JavaScript snippets that measure and debug web performance. Your AI agent runs them for you, or you run them yourself in DevTools: the same code every time.
AI agents are good at interpreting performance data and unreliable when they write measurement code on the fly. WebPerf Snippets keeps both apart: the measurement is fixed code, tested in CI, that returns structured data, and the agent reasons about the result. The same snippets run in the console, the CLI, the DevTools extension and the Agent Skills, and every one returns an object that follows a single contract (snippets/SCHEMA.md).
→ Why AI audits need deterministic scripts
| You want to | Use |
|---|---|
| Audit a URL with any agent that has a terminal | The Copy prompt to measure button on each snippet page |
| Give an agent the snippets as tools | The MCP server |
| Let the agent drive your Chrome (login, interactions) | The Agent Skills with Chrome DevTools MCP |
| Run snippets from scripts or CI | The CLI |
| Give an agent the whole documentation | llms.txt (details) |
Not sure which snippet to run? Start from the symptom in Which snippet should I use?
Snippet pages have a Copy prompt to measure button above the code. It copies a prompt that asks any AI agent with a terminal to run that snippet with the CLI on the URL you give it, and to report the value, the cause and the issues. The agent runs the published snippet instead of rewriting it or estimating the result.
The CLI includes an MCP server: an agent in any MCP client (Claude Code, Cursor, VS Code, Gemini CLI) calls the snippets and the workflows as tools, on a headless Chromium, and reads the object each one returns. It is listed in the MCP Registry as io.github.nucliweb/webperf-snippets.
claude mcp add webperf -- npx -y webperf-snippets mcp
In Claude Code, the webperf plugin installs the same server:
/plugin install webperf --marketplace nucliweb/webperf-snippets
See the MCP server documentation for other clients, the tools, the resources and prompts, and the CrUX key.
The snippets are packaged as Agent Skills for Claude Code, Cursor, OpenCode, Gemini CLI, VS Code extensions and other compatible agents. With Chrome DevTools MCP, the agent runs the snippets in your browser and rea