
WebSpeed MCP server
Which MCP servers are WebSpeed's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-29
- Registry namepro.webspeed/webspeedverified in the MCP registry
The registry name sits under webspeed.pro. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-29
- Tools2
- Server calls itselfwebspeed
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 633 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 4 of the 7 days it takes to judge reliability.
Once connected
- For "Check a site's before and after PageSpeed score for free", the likely first call is measure_site.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer647 ms
- Space in an agent's context≈ 311 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Route an existing site through a proxy without code changes
- can do · Check a site's before and after PageSpeed score for free
- not sure · Reduce page weight so mobile visitors see content sooner
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
measure_siteStart a real PageSpeed Insights measurement of a web page: the original site vs. its copy accelerated by WebSpeed Fast (mobile and desktop). Returns an audit_id immediately; the run takes 2–5 minutes, and get_measurement reads it when the…
get_measurementStatus or result of a measurement started with measure_site. While running, returns the queue position or progress. When done, returns the verified comparison and what else slows the page down. Quote numbers only from this result and keep…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"webspeed": {
"type": "http",
"url": "https://api.webspeed.pro/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http webspeed https://api.webspeed.pro/mcpclaude.ai, ChatGPT and other clients: add https://api.webspeed.pro/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.