dev.webanalyzer/webanalyzer
REMOTE · MCP.WEBANALYZER.DEV · SCANNED SEP 21
Free website analyzer: score any public URL 0-100 across 8 quality dimensions. No auth.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 450 tokens (~75/item across 6 items; 3 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the dev.webanalyzer/webanalyzer MCP server?
dev.webanalyzer/webanalyzer is a hosted endpoint at https://mcp.webanalyzer.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.webanalyzer.dev
claude mcp add --transport http dev-webanalyzer-webanalyzer 'https://mcp.webanalyzer.dev/'
{
"mcpServers": {
"dev-webanalyzer-webanalyzer": {
"url": "https://mcp.webanalyzer.dev/"
}
}
} {
"servers": {
"dev-webanalyzer-webanalyzer": {
"type": "http",
"url": "https://mcp.webanalyzer.dev/"
}
}
} [mcp_servers.dev-webanalyzer-webanalyzer] url = "https://mcp.webanalyzer.dev/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-webanalyzer-webanalyzer": {
"type": "remote",
"url": "https://mcp.webanalyzer.dev/",
"enabled": true
}
}
} openclaw mcp add dev-webanalyzer-webanalyzer --url 'https://mcp.webanalyzer.dev/' --transport streamable-http
mcp_servers:
dev-webanalyzer-webanalyzer:
url: "https://mcp.webanalyzer.dev/" {
"McpServers": {
"dev-webanalyzer-webanalyzer": {
"Transport": "http",
"Url": "https://mcp.webanalyzer.dev/"
}
}
} assistant mcp add dev-webanalyzer-webanalyzer -t streamable-http -u 'https://mcp.webanalyzer.dev/'
{
"mcpServers": {
"dev-webanalyzer-webanalyzer": {
"type": "http",
"url": "https://mcp.webanalyzer.dev/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyze_website” rewrote its description, which is the text the model reads security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Probed https://mcp.webanalyzer.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.webanalyzer.dev | CN=YR2,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | RSA 2048 | SHA256-RSA | 68719817258a74f6551044347983106f1db |
| SANs: *.webanalyzer.dev, webanalyzer.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.webanalyzer.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| webanalyzer.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.webanalyzer.dev | Verified | 200 | |
| http (plaintext) | http://mcp.webanalyzer.dev | HTTPS enforced | 308 | https://mcp.webanalyzer.dev/ |
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 →
analyze_website Analyze a website ~114
Analyze a public web page with WebAnalyzer's 290+ deterministic checks and return its 0-100 quality score, letter grade, per-dimension scores (SEO, GEO/AI readiness, performance, accessibility, code quality, UI/UX, data & tracking, security) and the top issues found. Free, no auth — 3 analyses per day. Not for localhost or pages behind a login.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the public page to analyze, e.g. https://example.com |
No output schema declared.
No examples provided.
get_analysis Get a stored analysis ~86
Fetch the result of a previous analyze_website run by its analysis id: the 0-100 score, grade, per-dimension scores and top issues. Ids come from analyze_website results and report URLs (webanalyzer.dev/report/<id>).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Analysis id returned by analyze_website (also the last segment of a report or badge URL). |
No output schema declared.
No examples provided.
get_leaderboard Get the leaderboard ~58
Return the public WebAnalyzer leaderboard: the highest-scoring analyzed websites with their name, URL and 0-100 score, best first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many entries to return (1-100). Default 20. |
No output schema declared.
No examples provided.
What is the dev.webanalyzer/webanalyzer MCP server?
dev.webanalyzer/webanalyzer is an MCP server listed in the public MCP registry as dev.webanalyzer/webanalyzer. Free website analyzer: score any public URL 0-100 across 8 quality dimensions. No auth. This page covers its hosted endpoint (https://mcp.webanalyzer.dev).
Is the dev.webanalyzer/webanalyzer MCP server safe to use?
dev.webanalyzer/webanalyzer scores 83 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 dev.webanalyzer/webanalyzer MCP server expose?
dev.webanalyzer/webanalyzer exposes 3 tools: analyze_website, get_leaderboard, get_analysis. Their descriptions and schemas cost roughly 258 tokens of context every time the server is loaded.
Does the dev.webanalyzer/webanalyzer MCP server require authentication?
No. We connected to dev.webanalyzer/webanalyzer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.webanalyzer/webanalyzer MCP server still maintained?
dev.webanalyzer/webanalyzer is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.