Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/corewebvitals/state-of-cwv-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/corewebvitals/state-of-cwv-mcp/state-of-cwv)<a href="https://agentmods.dev/mcp/corewebvitals/state-of-cwv-mcp/state-of-cwv"><img src="https://agentmods.dev/badge/mcp/corewebvitals/state-of-cwv-mcp/state-of-cwv/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/corewebvitals/state-of-cwv-mcp/state-of-cwv"><img src="https://agentmods.dev/badge/mcp/corewebvitals/state-of-cwv-mcp/state-of-cwv.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
state-of-cwv scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"state-of-cwv": {
"url": "https://www.corewebvitals.io/api/state-of-cwv/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 6 lines scan A ed7085604def
state-of-cwv is an MCP server published in the GitHub repository corewebvitals/state-of-cwv-mcp (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
xmemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST. Runs locally from the @xmemo/client npm package. Needs 2 environment variables to run.
mcp
Architecture docs and patterns for NestJS + Nuxt full-stack apps. Remote server at mcp.cleanslice.org.
mcp-web-validator
W3C HTML/CSS Validator and Technical SEO Audit MCP Server for AI coding assistants. Runs locally from the mcp-web-validator npm package.
mcp
AI-powered design and management for Webflow Sites. Remote server at mcp.webflow.com.
agent-audit
Turn Lighthouse audits into coding-agent fix packs for Claude Code, Cursor, and Copilot. Runs locally from the @fullstackdegen/agent-audit npm package.
wpf-visual-tree
MCP server "wpf-visual-tree" as configured in faze79/WPFVisualTreeMcp. Launched with WpfVisualTreeMcp.