Developer · Remote MCP server

Coredash

Real User Monitoring for Core Web Vitals. Query LCP, INP, CLS field data from real visitors.

Visit Coredash's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.corewebvitals/coredash
Version
1.0.1
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-05-11
Updated
2026-05-11
Publisher
corewebvitals (GitHub) · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/corewebvitals) · how
Website
coredash.app
Repository
github.com/corewebvitals/coredash-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://app.coredash.app/api/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
coredash-mcp 1.0.0 · protocol 2025-03-26
Tools discovered
Not listed - auth_required: HTTP 401
Checked on
2026-10-05

How the live check works

How to connect Coredash

Coredash is a remote MCP server: there is nothing to install. Its endpoint is https://app.coredash.app/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from corewebvitals (GitHub)

All 2 →
ServerRunsEndpoint or package
State of Web VitalsCore Web Vitals metrics by CMS, CDN, and framework - free remote MCP, no auth.Remote · HTTPLive check: ✓ handshakecorewebvitals.io

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Copyright01Copyright deposit API - protect code, text, and websites with Berne Convention proof.Remote · HTTPLive check: ✗ no handshakecopyright01.com
Coralquery MCPA paid remote MCP for AI SDK data query MCP, built to return verdicts, receipts, usage logs, and aud.Remote · HTTPLive check: ✗ no handshakecoralquery.clauxel.com
Cordon for MCPCordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals.Local · stdionpm: @getcordon/cli
CoReason Ecosystem - Federated MCP GatewayCoReason Tripartite Architecture Governance Plane. Stateless zero-trust federated MCP gateway.Local · stdioPyPI: coreason-ecosystem
CorpoleRequirements authority for AI coding agents: binding requirements and acceptance criteria.Remote · HTTPLive check: ✗ no handshakecorpole.com
corpusAI Cloud PricingCloud, GPU and LLM token prices with index fixings. Pay per call over x402 or with a prepaid key.Remote & Local · HTTP, stdioLive check: ✓ handshakecloud.trycorpus.ai
CorralSearch code and symbols across every clone in your Corral workspace. Zero network calls.Local · stdioOCI image (Docker): ghcr.io/sebastienrousseau/corral:0.0.36
corralctlSearch code and symbols across every clone in your corralctl workspace. Zero network calls.Local · stdioOCI image (Docker): ghcr.io/sebastienrousseau/corralctl:0.0.41