mcpbeat Sign in

Browser Compat MCP Server

answering

Browser Compat MCP Server is answering right now. Last checked 4 min ago. 457 installs a week from npm. It exposes 5 tools. Last commit 20 Sep 2026.

Browser compatibility and Baseline status for any web feature — offline, from bundled MDN data.

Installs per day peak 457 · avg 15
a month agotoday
Uptime history 30 hours of history · worst hour 75%
30 hours agonow
98.9%
Uptime 24h
90 of 91 checks
5
Tools
read from the server
409 ms
Response time
average over 24h
457
Installs / week
npm and PyPI

Browser Compat MCP Server does not always answer

Over the last week it answered 99.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add browser-compat-mcp-server --transport http https://browser-compat.caseyjhand.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "url": "https://browser-compat.caseyjhand.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.browser-compat-mcp-server]
url = "https://browser-compat.caseyjhand.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "url": "https://browser-compat.caseyjhand.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "browser-compat-mcp-server": {
      "url": "https://browser-compat.caseyjhand.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: MCP_HTTP_HOST (The hostname for the HTTP server.), MCP_HTTP_PORT (The port to run the HTTP server on.), MCP_HTTP_ENDPOINT_PATH (The endpoint path for the MCP server.), MCP_AUTH_MODE (Authentication mode to use: 'none', 'jwt', or 'oauth'.), MCP_LOG_LEVEL (Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').). The author declared them in the registry entry; get the values from the project itself.

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

browsercompat
browsercompat_check_baseline
Check whether web features are safe to ship: Baseline state and the date it crossed, the browser and version that limits support, whether the feature is deprecated or discouraged, and the share of tracked global traffic that requiring it would exclude. Accepts up to 20 BCD keys or web-features ids in one call.
browsercompat_compare_support
Compute whether a set of web features clears an explicit browserslist target query. Returns a per-feature verdict, the target browser and version that fails, the share of tracked traffic the targets cover, and unchecked_targets for every resolved target browser with no compatibility data. A feature is never reported as clearing a target the server could not evaluate.
browsercompat_get_feature
Get the compatibility record for one web feature: Baseline state and the date it crossed, deprecation and standards status, per-browser version added and removed with flags, vendor prefixes and partial-implementation notes, and the MDN and specification links. Accepts a BCD key such as css.selectors.has or a web-features id such as has; the response echoes which one it matched. An unresolved feature returns found: false with guidance rather than an error.
browsercompat_list_reference
Enumerate the reference vocabulary this server uses: BCD namespaces, BCD browser ids, browserslist agent ids and their BCD counterparts, Baseline states, web-features groups, and ECMAScript snapshots. Use it to build valid inputs for the other tools and to see which target browsers can be evaluated.
browsercompat_search_features
Find web features by plain name or keyword when the canonical key is unknown, across CSS, JavaScript, HTML, Web APIs, SVG, MathML, WebAssembly, and HTTP headers. Returns ranked matches with the BCD key, the web-features id, the Baseline state, a one-line support summary, and which field matched. Feed a result key into browsercompat_get_feature for the full record.

Endpoints

URLTransportStateLatencyChecked
https://browser-compat.caseyjhand.com/mcp streamable-http answering 412 ms 4 min ago

Alternatives to Browser Compat MCP Server

same job, measured the same way
CSS SOTA
by lusrodri

What CSS you can actually ship today, from live Baseline data and MDN browser-compat-data.

6 tools answering
Can I Use
by kaiv

Browser support for web features, live from caniuse. From which version, and is it safe to ship?

3 tools answering
MCP Server Browserbase
by browserbase

MCP server for AI web browser automation using Browserbase and Stagehand

4 036 installs/wk local only
Skyvern
by skyvern-ai

AI-powered browser automation — navigate, click, fill forms, and extract data from any website.

answering
I
Utility Matrix
by helphub369

Free browser-based calculators and analyzers for cloud cost, DevOps, security, and data governance.

31 tools answering
Crumbtrail
by crumbtraildev

Recorded browser sessions, backend spans, and database row diffs as one ranked fix bundle.

97 installs/wk local only
shaft-mcp
by shafthq

SHAFT browser automation, capture, and offline deterministic failure diagnosis

local only
openDAW MCP
by ameobius

262 MCP tools for agent-native control of openDAW, a browser-based DAW

local only

Browser Compat MCP Server — questions

Answers built from our own checks of this server.

What can Browser Compat MCP Server do?
It exposes 5 tools, read directly from the server on our last check. Among them: browsercompat_check_baseline, browsercompat_compare_support, browsercompat_get_feature, browsercompat_list_reference, browsercompat_search_features. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Browser Compat MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 409 ms. The bar chart above shows every period we have measured.
How do I connect Browser Compat MCP Server?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Browser Compat MCP Server need an API key?
No. Browser Compat MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Browser Compat MCP Server?
It answers our handshake in 409 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Browser Compat MCP Server?
The npm package @cyanheads/browser-compat-mcp-server was installed 457 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Browser Compat MCP Server open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 7 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.