Google CrUX MCP

io-github-a1-x-tech-mcp-google-crux declares 6 capabilities across 6 tools, with 1 critical issue.

11/100 exposureLow exposure

Manifest recorded 2026-10-11 from tools/list answered by the npm package mcp-google-crux@1.1.0 (published to npm as mcp-google-crux, listed in the official MCP registry as io.github.A1-x-Tech/mcp-google-crux 1.1.0), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 6 tools

6 of 6 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

high · no-expiry · All 6 tools

6 of 6 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 6 tools

6 of 6 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

low · uncapped-read · All 6 tools

6 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

Tool	Read as	Basis
`get_core_web_vitals`	`read`	declared
`compare_form_factors`	`read`	declared
`compare_origin_vs_url`	`read`	declared
`get_cwv_trend`	`read`	declared
`query_record`	`read`	declared
`query_history_record`	`read`	declared

Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.

Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.