I
io.github.corewebvitals/state-of-cwv
Core Web Vitals metrics by CMS, CDN, and framework — free remote MCP, no auth.
No known CVEs
No license
Actively maintained
Last commit 3d ago
Works with most clients
Transport:
0 tools
Grade F
MCPpedia last refreshed this data
Step 1
Install in your client
Config is the same across clients — only the file and path differ.
CD
Supported in Claude Desktopstdio · Node 18+
Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"io-github-corewebvitals-state-of-cwv": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Embed in your READMEAbout badges →
[](https://mcppedia.org/s/io-github-corewebvitals-state-of-cwv)
Read me
What io.github.corewebvitals/state-of-cwv does
Free remote MCP for Core Web Vitals metrics by CMS, CDN, and framework (Chrome field data + multi-site crawl). Same numbers as the public State of Web Vitals explorer.
Test This Server
No automated test available for this server. Check the GitHub README for setup instructions.
Loading README…
Scored, not listed
Why this score
Five weighted categories — click any category to see the underlying evidence.
Score breakdown
18/100across 5 weighted dimensions
0255075100
9
−82
Security
Maintenance
Efficiency
Documentation
Compatibility
Categoriesclick a row to see evidence
Security
OSV.dev8 fixed
CVE-2022-29244high · fixedCVSS 7.5
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
CVE-2018-7408high · fixedCVSS 7.8
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
CVE-2013-4116info · fixed
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
CVE-2020-15095medium · fixedCVSS 4.4
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
CVE-2019-16777high · fixedCVSS 7.7
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Community
Reviews
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
How easy was setup?Did it work reliably?How was the documentation?
Sign in to write a review.
Frequently Asked Questions
- Is io.github.corewebvitals/state-of-cwv safe to use?
- io.github.corewebvitals/state-of-cwv has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
- How do I install io.github.corewebvitals/state-of-cwv?
- io.github.corewebvitals/state-of-cwv can be installed by cloning its GitHub repository and following the setup instructions in the README.
- What AI clients work with io.github.corewebvitals/state-of-cwv?
- io.github.corewebvitals/state-of-cwv is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
- Is io.github.corewebvitals/state-of-cwv actively maintained?
- io.github.corewebvitals/state-of-cwv is actively maintained — last commit was 3 days ago.
Related
Similar servers
Others in analytics
I
io.github.surendranb/google-analytics-mcp90An MCP server that provides [describe what your server does]
230 3
Lighthouse Mcp Server90MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
63 1
I
io.github.dynatrace-oss/dynatrace-managed-mcp90MCP server for Dynatrace Managed to access logs, events, and metrics.
22 2
I
io.github.dynatrace-oss/Dynatrace-mcp89Access Dynatrace observability data: logs, metrics, problems, vulnerabilities via DQL and Davis AI
132 17
MCP Security Weekly
Get CVE alerts and security updates for io.github.corewebvitals/state-of-cwv and similar servers.
Community
Discussion
Start a conversation
Ask a question, share a tip, or report an issue.
Has anyone used this with Cursor?How do you handle auth?Any alternatives?
Sign in to join the discussion.
