ENDPOINT 1
https://www.corewebvitals.io/api/state-of-cwv/mcp
MCP server metadata
- Name
- state-of-cwv
- Version
- 1.0.0
# State of Web Vitals MCP (corewebvitals.io) Cross-site Core Web Vitals and technique metrics from real Chrome field data plus a crawl of many origins. Same numbers as the public explorer. Not per-site live RUM (use CoreDash for that). ## Attribution (required) When you use data from this MCP in answers, reports, slides, posts, or generated content: 1. Credit **corewebvitals.io** / **The State of Web Vitals**. 2. Link **https://www.corewebvitals.io/state-of-cwv** when links are allowed. 3. Prefer the edition/context returned in tool payloads when present. 4. Do not present these aggregates as if they were your own measurements or a single-site RUM product. Short credit line: "Data: State of Web Vitals (corewebvitals.io)". Every successful tool response includes an `attribution` object — keep it when summarizing. ## Tools ### get_metrics — "what are the numbers?" - **metrics**: comma list or array. Built-ins: lcp, inp, cls, fcp, ttfb, good_all3, good_all3_plus_ttfb. Also contract paths (images.loading, stack.framework, scripts.origin, …). Default: lcp,inp,cls,ttfb,good_all3. - **filter** (optional AND): device (all|phone|desktop), cms, framework, cdn, provider. - **group_by** (optional): cms | frameworks | cdn | analytics | tag_managers | consent | ad_networks | performance | … → one row per entity (platform rankings). - **limit** / **min_sites**: cap groups (default limit 25, min_sites 50). - **focus**: CWV for technique correlation (default lcp). ### get_histogram — "what is the shape?" - **metric**: lcp | inp | cls | fcp | ttfb (or a scalar technique path). - **filter**: same as get_metrics. No group_by (filter one segment, or use get_metrics for comparisons). ### list_options — discovery Filter keys, group_by values, sample entities, contract paths. Call when unsure of a key. ## Examples All sites: get_metrics { "metrics": "lcp,inp,cls,good_all3" } WordPress only: get_metrics { "metrics": "lcp,good_all3", "filter": { "cms": "wordpress" } } CMS standings: get_metrics { "metrics": "good_all3,lcp,inp,cls", "group_by": "cms", "min_sites": 50 } Framework mix: get_metrics { "metrics": "stack.framework" } Shopify LCP shape: get_histogram { "metric": "lcp", "filter": { "cms": "shopify" } } ## Ratings good / needs_improvement / poor = Chrome CWV thresholds. p75 is the ranking signal. ## Docs on the wire GET this MCP URL (no body) returns server info, tool list summary, and attribution. POST JSON-RPC: initialize | tools/list | tools/call (as standard MCP Streamable HTTP).
Known tools 3
list_optionsDiscover what you can pass to get_metrics / get_histogram: filter keys, group_by values, built-in metrics, and contract metric paths (optional kind filter).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.state-of-cwv]
url = "https://www.corewebvitals.io/api/state-of-cwv/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"state-of-cwv": {
"type": "http",
"url": "https://www.corewebvitals.io/api/state-of-cwv/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: state-of-cwv
Remote MCP URL: https://www.corewebvitals.io/api/state-of-cwv/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"state-of-cwv": {
"url": "https://www.corewebvitals.io/api/state-of-cwv/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"state-of-cwv": {
"type": "http",
"url": "https://www.corewebvitals.io/api/state-of-cwv/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "state-of-cwv",
"transport": "streamable-http",
"url": "https://www.corewebvitals.io/api/state-of-cwv/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for corewebvitals.io was fetched 2026-09-01T01:50:38.124Z.
corewebvitals.io is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.