WSG Check
NPM · @SUSTAINABLEWEBSITES/WSG-CHECK · SCANNED OCT 3
Check websites against the W3C Web Sustainability Guidelines and look up the guidelines
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 38 of 133 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ivanoats/wsg-check). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 488 tokens (~162/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
How do I install the WSG Check MCP server?
WSG Check runs locally as an npm package, launched with npx -y @sustainablewebsites/wsg-check. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @sustainablewebsites/wsg-check
claude mcp add ivanoats-wsg-check -- npx -y @sustainablewebsites/wsg-check
{
"mcpServers": {
"ivanoats-wsg-check": {
"command": "npx",
"args": [
"-y",
"@sustainablewebsites/wsg-check"
]
}
}
} {
"servers": {
"ivanoats-wsg-check": {
"command": "npx",
"args": [
"-y",
"@sustainablewebsites/wsg-check"
]
}
}
} codex mcp add ivanoats-wsg-check -- npx -y @sustainablewebsites/wsg-check
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ivanoats-wsg-check": {
"type": "local",
"command": [
"npx",
"-y",
"@sustainablewebsites/wsg-check"
],
"enabled": true
}
}
} openclaw mcp add ivanoats-wsg-check --command npx --arg -y --arg @sustainablewebsites/wsg-check
mcp_servers:
ivanoats-wsg-check:
command: "npx"
args: ["-y", "@sustainablewebsites/wsg-check"] {
"McpServers": {
"ivanoats-wsg-check": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@sustainablewebsites/wsg-check"
]
}
}
} assistant mcp add ivanoats-wsg-check -t stdio -c npx -a -y @sustainablewebsites/wsg-check
{
"mcpServers": {
"ivanoats-wsg-check": {
"command": "npx",
"args": [
"-y",
"@sustainablewebsites/wsg-check"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 80
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Oct 2026 · Analysed npm/@sustainablewebsites/wsg-check@0.6.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ivanoats/wsg-check |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ivanoats/wsg-check/.github/workflows/publish.yml@refs/tags/v0.6.0 |
| Rekor log index | 2969527643 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:20ccae6e900fe9a9c0412554210dc307ed19effd5078782eec2b4a550d49904cf95dba1dab487c2a819ce94d3e1dcda9ac708b832cb2af602bac1abca |
Background: How many MCP packages publish verified provenance →
Dependencies 133 packages
| Packages resolved | 133 |
|---|---|
| Deprecated | 1 |
| Stale | 38 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_url Check a URL against the WSG ~200
Fetches a page and checks it against the W3C Web Sustainability Guidelines. Returns the score, grade, and each failed or warned check with a recommended fix. Local URLs such as http://localhost:3000 are fetched from the user's machine; they work unless the server was started with --no-local.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | WSG categories to run. Defaults to all three. |
| detail | string | – | "summary" (default) returns the score and the failed or warned checks. "full" also returns the complete report, which is much longer. |
| guidelines | array | – | Narrow the run to these guideline slugs (e.g. "minify-and-remove-unused-code") or related-check IDs. |
| timeoutMs | integer | – | Give up after this many milliseconds. Defaults to 60000. |
| url | string | yes | The page to check, e.g. https://example.com or http://localhost:3000 |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | – |
| report | object | – | The complete report; present only when detail is "full" |
| summary | object | yes | – |
No examples provided.
get_guideline Get a WSG guideline ~84
Returns one guideline: its description, category, testability, W3C specification link, and how many automated checks implement it. Accepts a slug, or a deprecated numeric ID such as "3.3", which is resolved to its current slug.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A guideline slug such as "minify-and-remove-unused-code", or a legacy number |
| Name | Type | Req | Description |
|---|---|---|---|
| guideline | object | yes | – |
| notices | array | yes | Notes about the request, e.g. a deprecated ID |
| spec | object | yes | – |
No examples provided.
list_guidelines List WSG guidelines ~120
Lists the guidelines in WSG July-2026, optionally filtered by category, testability, or text in the title, slug, or description. Each entry has the slug to pass to get_guideline or to check_url's guidelines, and how many automated checks implement it.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only guidelines in this category |
| query | string | – | Case-insensitive text to find in the title, slug, or description, e.g. "media" |
| testability | string | – | Only guidelines that can be tested this way |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| guidelines | array | yes | – |
| spec | object | yes | – |
No examples provided.
What is the WSG Check MCP server?
WSG Check is an MCP server listed in the public MCP registry as io.github.ivanoats/wsg-check. Check websites against the W3C Web Sustainability Guidelines and look up the guidelines. This page covers its npm package (@sustainablewebsites/wsg-check).
Is the WSG Check MCP server safe to use?
WSG Check scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 WSG Check MCP server expose?
WSG Check exposes 3 tools: check_url, list_guidelines, get_guideline. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.
Is the WSG Check MCP server still maintained?
WSG Check is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the WSG Check MCP server under?
WSG Check declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.