_ registry / mcp streamable-http · checked 12m ago

state-of-cwv

https://www.corewebvitals.io

Registry code: c9ddc5f3344fb0f3

api record

# 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).

endpoint
https://www.corewebvitals.io/api/state-of-cwv/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is state-of-cwv live?
Yes — it answered the hub's last check (checked 12m ago). It answered 100% of checks over the last 30 days.
Is state-of-cwv free to use?
Yes — the hub reached it with no key and no payment.
What tools does state-of-cwv have?
3 tools: get_histogram, get_metrics, list_options.
Is state-of-cwv safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
119ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 530 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get aggregate core web vitals metrics
  • get a histogram of a web vitals metric
  • list available filters and metrics
takes → gives
data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_metrics reads open 9h ago

    What are the numbers? Aggregate Core Web Vitals and/or technique metrics across sites, with optional filter and group_by. Responses include attribution — credit corewebvitals.io when you use the numbers. Metrics (comma-separated or array): - CWV: lcp, inp, cls, fcp, ttfb — good/needs_improvement/poor share + p50/p75 + sample n - good_all3 — share of sites that pass LCP+INP+CLS together - good_all3_plus_ttfb — pass all three plus TTFB - Contract paths: images.loading, stack.framework, scripts.origin, headers.has_etag, synthetic.tbt_ms, … Filter (optional AND): device, cms, framework, cdn, provider. Omit = all sites in the snapshot. Group_by (optional): cms | frameworks | cdn | analytics | tag_managers | … → one row per entity. Without group_by: one aggregate; set metrics return top categories.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "focus": {
          "enum": [
            "lcp",
            "inp",
            "cls",
            "fcp",
            "ttfb"
          ],
          "type": "string",
          "description": "CWV used when correlating technique metrics. Default: lcp."
        },
        "limit": {
          "type": "integer",
          "description": "Max groups or top categories. Default: 25, max: 100."
        },
        "filter": {
          "type": "object",
          "properties": {
            "cdn": {
              "type": "string",
              "description": "Only sites on this CDN key (cloudflare, origin, …)."
            },
            "cms": {
              "type": "string",
              "description": "Only sites on this CMS key (wordpress, shopify, wix, …)."
            },
            "device": {
              "enum": [
                "all",
                "phone",
                "desktop"
              ],
              "type": "string",
              "description": "CrUX device slice. Default: all."
            },
            "provider": {
              "type": "string",
              "description": "Only sites that load this third-party provider key (google_analytics_4, …)."
            },
            "framework": {
              "type": "string",
              "description": "Only sites that include this JS framework key (react, vue, jquery, …)."
            }
          },
          "description": "AND filters. Omit for all sites in the dataset. Keys: device (all|phone|desktop), cms, framework, cdn, provider (key), provider_category (e.g. analytics — use with provider or alone is not enough; prefer group_by for rankings).",
          "additionalProperties": false
        },
        "metrics": {
          "description": "Metrics to return. Default: lcp,inp,cls,ttfb,good_all3. String (comma-separated) or array of strings."
        },
        "group_by": {
          "type": "string",
          "description": "Break results down by this dimension: cms, frameworks, cdn, or a provider category (analytics, tag_managers, …). Omit for a single aggregate."
        },
        "min_sites": {
          "type": "integer",
          "description": "When group_by is set, drop groups with fewer sites. Default: 50."
        }
      }
    }
    arguments 63 lines
  • list_options reads open 9h ago

    Discover what you can pass to get_metrics / get_histogram: filter keys, group_by values, built-in metrics, and contract metric paths (optional kind filter). Call this when unsure of a key or path.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kind": {
          "type": "string",
          "description": "Optional contract kind: scalar, boolean, categorical, set, weighted_set, measures."
        },
        "include_paths": {
          "type": "boolean",
          "description": "Include full contract path list. Default true."
        }
      }
    }
    arguments 13 lines
  • get_histogram reads unknown 9h ago

    What is the shape of one metric? Returns histogram buckets (count + share) plus summary stats. Metric: one of lcp, inp, cls, fcp, ttfb (field CWV), or a scalar technique path when available. Filter: same as get_metrics (device, cms, framework, cdn, provider). No group_by — call get_metrics with group_by to compare segments, then get_histogram per segment if needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "metric"
      ],
      "properties": {
        "filter": {
          "type": "object",
          "properties": {
            "cdn": {
              "type": "string",
              "description": "Only sites on this CDN key (cloudflare, origin, …)."
            },
            "cms": {
              "type": "string",
              "description": "Only sites on this CMS key (wordpress, shopify, wix, …)."
            },
            "device": {
              "enum": [
                "all",
                "phone",
                "desktop"
              ],
              "type": "string",
              "description": "CrUX device slice. Default: all."
            },
            "provider": {
              "type": "string",
              "description": "Only sites that load this third-party provider key (google_analytics_4, …)."
            },
            "framework": {
              "type": "string",
              "description": "Only sites that include this JS framework key (react, vue, jquery, …)."
            }
          },
          "description": "AND filters. Omit for all sites in the dataset. Keys: device (all|phone|desktop), cms, framework, cdn, provider (key), provider_category (e.g. analytics — use with provider or alone is not enough; prefer group_by for rankings).",
          "additionalProperties": false
        },
        "metric": {
          "type": "string",
          "description": "lcp | inp | cls | fcp | ttfb, or a contract scalar path."
        }
      }
    }
    arguments 44 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c9ddc5f3344fb0f3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c9ddc5f3344fb0f3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c9ddc5f3344fb0f3/badge.svg)](https://brick.blue/agent/c9ddc5f3344fb0f3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.