# Browserslist and caniuse checker (mcpb · browserslist-check-1.0.0.mcpb)

Exact browsers a browserslist query targets, and whether a CSS/JS feature works in all (caniuse)

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `browserslist-check-1.0.0.mcpb`: 40/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check.md), [page](https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check)
- oci · `ghcr.io/lawatch/browserslist-check`: 40/100, [markdown](https://verifymcp.io/servers/lawatch-browserslist-check/ghcr-io-lawatch-browserslist-check.md), [page](https://verifymcp.io/servers/lawatch-browserslist-check/ghcr-io-lawatch-browserslist-check)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Lawatch/10aday/releases/download/browserslist-check-v1.0.0/browserslist-check-1.0.0.mcpb`
- Transport: `stdio`
- SHA-256: `6056073bdee0b7007e71bb3d0fdc431d686e79b7ee935e29fc926c6db3b78567`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 959 tokens (~319/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Browserslist and caniuse checker MCP server?

Browserslist and caniuse checker ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 6056073bdee0b7007e71bb3d0fdc431d686e79b7ee935e29fc926c6db3b78567; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Lawatch/10aday/releases/download/browserslist-check-v1.0.0/browserslist-check-1.0.0.mcpb`
- SHA-256: `6056073bdee0b7007e71bb3d0fdc431d686e79b7ee935e29fc926c6db3b78567`

### Verify on macOS / Linux

```bash
echo "6056073bdee0b7007e71bb3d0fdc431d686e79b7ee935e29fc926c6db3b78567  browserslist-check-1.0.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\browserslist-check-1.0.0.mcpb).Hash -eq "6056073bdee0b7007e71bb3d0fdc431d686e79b7ee935e29fc926c6db3b78567"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 38)

First indexed and scored.

## MCP tools (3)

### `resolve_browsers` (~381 tokens)

Which browsers does this browserslist query target?

Runs the real browserslist (the code Babel, Autoprefixer, PostCSS, Vite, esbuild-plugin-browserslist and SWC use) on a query or on a .browserslistrc / package.json config, with up-to-date caniuse data, and returns the exact browser versions, the share of world (and country) usage they cover, what each part of the query adds or removes, and the traps: dead browsers, Opera Mini, IE, empty result, wrong config section. Use it instead of guessing what "defaults", "> 0.5%", "last 2 versions" or "cover 95%" mean today.

Input parameters:

- `config` (string|array|object): Instead of query: the text of .browserslistrc, or the value of the "browserslist" key of package.json (string, array, or object with environments like { "production": [...], "development": [...] }).
- `env` (string): Config section to use (like BROWSERSLIST_ENV / NODE_ENV). Default "production", then "defaults".
- `mobile_to_desktop` (boolean): Same as the browserslist mobileToDesktop option (used by Babel and Autoprefixer through their own settings).
- `package_json` (object|string): Instead of query/config: the whole package.json; its "browserslist" key is read.
- `query` (string|array): A browserslist query, e.g. "> 0.5%, last 2 versions, not dead" or ["defaults", "not op_mini all"]. Wins over config.
- `region` (string): Optional country code ("US", "FR", "IN") or "alt-eu", "alt-as"… to also get usage shares there.

### `check_support` (~388 tokens)

Can I use this web feature with my browserslist targets?

For one or more web features (caniuse ids or names: "css-has", ":has", "structuredClone", "dialog", "container queries", "fetch", "es6-module"…), checks every target browser version from the query/config with the caniuse data: fully supported, partial, needs a vendor prefix, behind a flag, or missing; which browsers fail and their usage share; the first version with full support per browser; and a plain verdict. Use it before using a modern CSS/JS/HTML feature, or to decide if a polyfill or fallback is needed.

Input parameters:

- `config` (string|array|object): Instead of query: the text of .browserslistrc, or the value of the "browserslist" key of package.json (string, array, or object with environments like { "production": [...], "development": [...] }).
- `env` (string): Config section to use (like BROWSERSLIST_ENV / NODE_ENV). Default "production", then "defaults".
- `features` (array|string, required): caniuse feature ids or names. A name that matches several features returns the candidates.
- `mobile_to_desktop` (boolean): Same as the browserslist mobileToDesktop option (used by Babel and Autoprefixer through their own settings).
- `package_json` (object|string): Instead of query/config: the whole package.json; its "browserslist" key is read.
- `query` (string|array): A browserslist query, e.g. "> 0.5%, last 2 versions, not dead" or ["defaults", "not op_mini all"]. Wins over config.
- `region` (string): Optional country code ("US", "FR", "IN") or "alt-eu", "alt-as"… to also get usage shares there.

### `find_feature` (~83 tokens)

Find the caniuse id of a web feature

Searches the caniuse feature list (id and title) and returns the matching ids with their world support share. Use it to get the right id for check_support or for a "supports <feature>" browserslist query.

Input parameters:

- `limit` (integer)
- `query` (string, required): Words, e.g. "subgrid", "view transitions", "webp".

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check#diagnostics

## Score history

- 2026-11-21: 40
- 2026-11-20: 39
- 2026-11-19: 39
- 2026-11-18: 38
- 2026-11-17: 38

## Common questions

### What is the Browserslist and caniuse checker MCP server?

Browserslist and caniuse checker is an MCP server listed in the public MCP registry as io.github.Lawatch/browserslist-check. Exact browsers a browserslist query targets, and whether a CSS/JS feature works in all (caniuse). This page covers its MCPB bundle (https://github.com/Lawatch/10aday/releases/download/browserslist-check-v1.0.0/browserslist-check-1.0.0.mcpb).

### Is the Browserslist and caniuse checker MCP server safe to use?

Browserslist and caniuse checker scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Browserslist and caniuse checker MCP server expose?

Browserslist and caniuse checker exposes 3 tools: resolve_browsers, check_support, find_feature. Their descriptions and schemas cost roughly 852 tokens of context every time the server is loaded.

### What licence is the Browserslist and caniuse checker MCP server under?

Browserslist and caniuse checker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Browserslist and caniuse checker MCP server?

VerifyMCP ran 12 checks on Browserslist and caniuse checker, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Browserslist and caniuse checker: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-browserslist-check/browserslist-check
