browser-compat-mcp-server
io.github.cyanheads/browser-compat-mcp-servercyanheadsstreamable-httpv0.3.1Scanned
Browser compatibility and Baseline status for any web feature — offline, from bundled MDN data.
5 tools: 1 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the browser-compat-mcp-server can do
The browser-compat-mcp-server is published by the GitHub account cyanheads. It has 5 tools. It can create or change data (1 tool: browsercompat_check_baseline), but cannot delete data. 4 tools only read.
1 tool reads private data (browsercompat_get_feature); 4 tools bring in text other people can write (browsercompat_list_reference, browsercompat_get_feature, browsercompat_search_features and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.3.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
browsercompat_check_baselineCheck 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, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 percentage points of global traffic that requiring it would exclude. Evaluates up to 20 BCD keys or web-features ids per call; up to 100 may be sent, and entries past the 20th come back unevaluated in omitted_features for the next call.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
browsercompat_compare_supportCompute whether a set of web features clears an explicit browserslist target query.Reads text others writeNo findings
Why it is in this group
- The name "browsercompat_compare_support" says "compare": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "web": it reads web pages, which anyone can write.
Description, as the server wrote it Compute whether a set of web features clears an explicit browserslist target query. Compares up to 20 features per call; up to 100 may be sent, and entries past the 20th come back unevaluated in omitted_features for the next call. Every call evaluates the whole query: each feature gets a verdict, the count of failing targets, those targets grouped into runs of consecutive query targets per browser in failing_ranges, and its own evaluated and unevaluated target counts with the percentage points of global traffic each covers. The target rows behind those numbers — which release each target maps to, which targets were not evaluated and why, and the failing and unevaluated targets of each feature, a failing row carrying the prefix, alternative name, or flag behind its verdict — cover target_limit query targets per call, 10 by default and up to 1000; page through them with target_offset, and the verdicts, coverage, and totals stay identical on every page. A target counts as evaluated only where compatibility data was read for it, so a feature clears only when every target in the query was evaluated and supports it, and is inconclusive otherwise — a query that includes a browser with no compatibility data, as "defaults" does, never clears. A BCD key is judged on its own per-browser support. A web-features id spanning several keys, such as grid, is judged on the release web-features lists for the feature as a whole in each Baseline core browser, as support_source says; its other browsers are not evaluated.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
browsercompat_get_featureGet 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…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "browsercompat_get_feature" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "note": it reads notes.
- untrusted-inputThe description's first sentence says "get" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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 — with every other support statement recorded for that browser, such as an earlier prefixed or flagged release, in other_statements — 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. A web-features id that spans several BCD keys, such as grid, returns web-features’ own feature-level release per Baseline core browser in feature_support and its compat_keys, 100 per page, in place of per-key fields. An unresolved feature returns found: false with guidance rather than an error.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
browsercompat_list_referenceEnumerate the reference vocabulary this server uses: BCD namespaces, BCD browser ids, browserslist agent ids and their BCD counterparts, Baseline states, web-features groups, and E…Reads text others writeNo findings
Why it is in this group
- The name "browsercompat_list_reference" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
browsercompat_search_featuresFind 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.Reads text others writeNo findings
Why it is in this group
- The name "browsercompat_search_features" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "find" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://browser-compat.caseyjhand.com/mcp: tools/list returned 5 tools to an anonymous client, including browsercompat_check_baseline (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:browsercompat_compare_supportOnly readsdescriptioninputSchema
- Changed:browsercompat_list_referenceOnly readsinputSchema
- Changed:browsercompat_search_featuresOnly readsinputSchema
Tools2 changed.~2 changedView diff
- Changed:browsercompat_check_baselineChanges thingsdescription
- Changed:browsercompat_compare_supportOnly readsdescriptioninputSchema
Install
Pinned to version 0.3.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http browser-compat https://browser-compat.caseyjhand.com/mcpclaude mcp add --transport http browser-compat https://browser-compat.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__browser-compat__browsercompat_list_reference",
"mcp__browser-compat__browsercompat_get_feature",
"mcp__browser-compat__browsercompat_search_features",
"mcp__browser-compat__browsercompat_compare_support"
],
"ask": [
"mcp__browser-compat__browsercompat_check_baseline"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as browser-compat. Review it before you use it.
Capability tags behind 4 rules
- mcp__browser-compat__browsercompat_list_reference untrusted-input
- mcp__browser-compat__browsercompat_get_feature private-data, untrusted-input
- mcp__browser-compat__browsercompat_search_features untrusted-input
- mcp__browser-compat__browsercompat_compare_support untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/browser-compat-mcp-server/verify?hash=1d959d31ba5fc245f6263cd1eb0ad565d090eeec4a27b1ec9090749695bd4a94" | jq -e '.changed == false'Pinned hash 1d959d31ba5f, from Nov 11, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/browser-compat-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/browser-compat-mcp-server)Source: MCP Registry · repository. Synced Nov 11, 2026, 11:18 UTC.
browser-compat-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the browser-compat-mcp-server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the browser-compat-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the browser-compat-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the browser-compat-mcp-server have?
- 5 tools: 1 write, 4 read. browsercompat_check_baseline, browsercompat_list_reference, browsercompat_get_feature, browsercompat_search_features and browsercompat_compare_support.
Does the browser-compat-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the browser-compat-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the browser-compat-mcp-server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.