Evolize
REMOTE · EVOLIZE.COM
Accessibility scans with evidence, public reports, and fresh checks after fixes.
Available components
Last scanned (3 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 19 Oct 2026.
Category Testing and QA
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 17 Oct 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 66
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 19 Oct 2026 · Probed https://evolize.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=evolize.com | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 83b042e3adabe811139b54b0a1c71eff |
| SANs: evolize.com, app.evolize.com, *.app.evolize.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of evolize.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| evolize.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://evolize.com/api/mcp | HTTP error | 404 | |
| http (plaintext) | http://evolize.com/api/mcp | Inconclusive | 404 |
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 →
get_public_report Get an existing public accessibility report ~197
Retrieve an EXISTING public Evolize accessibility assessment for a website. Read-only: this starts no scan and creates no work. Returns not_found when no public report exists for the target — which says nothing about whether the site has accessibility problems. Evolize inspects publicly reachable pages of the target website in a real browser and runs deterministic accessibility checks (axe-core plus Evolize rules). It is not a local browser agent and it does not read your source code: findings reference the rendered DOM, so your coding agent maps them to source using its own repository access.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. Omit for the first page. |
| limit | integer | – | Findings per page. Default 20, maximum 50. |
| url | string | yes | The public website to assess, e.g. `example.com` or `https://example.com`. Not an Evolize URL. |
No output schema declared.
No examples provided.
get_scan_result Read an assessment result ~143
Read the result of an Evolize assessment started with scan_website, using the scan_handle it returned. Read-only: it never starts a scan, never refreshes an assessment, never changes publication state, and never consumes scan quota — polling is safe. While the assessment is pending it returns the status and a retry_after_seconds. Follow next_cursor to read every finding.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response's `next_cursor`. Omit for the first page. |
| limit | integer | – | Findings per page. Default 20, maximum 50. |
| scan_handle | string | yes | The opaque handle returned by scan_website. |
No output schema declared.
No examples provided.
scan_website Request an accessibility assessment ~208
Request an Evolize accessibility assessment of a publicly reachable website, then read the result with get_scan_result. By default a completed assessment up to 24 hours old is reused; pass refresh=true to require newly executed work (for example after deploying a fix). This CREATES work: it can start a real browser-based scan whose result is retained and may become a public report under Evolize's existing publication policy. Free public assessments are bounded: a completed result up to 24h old is reused unless refresh=true, at most 3 newly executed assessments per website per 24h, and the platform's own per-IP, per-domain and global scan limits still apply.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Require newly executed work instead of reusing a recent completed assessment. Use after deploying a fix. Never satisfied by an older completed report. |
| url | string | yes | The public website to assess, e.g. `example.com` or `https://example.com`. Not an Evolize URL. |
No output schema declared.
No examples provided.
How do I install the Evolize MCP server?
Evolize is a hosted endpoint at https://evolize.com/api/mcp, 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 · evolize.com
claude mcp add --transport http com-evolize-accessibility-scanner 'https://evolize.com/api/mcp'
What is the Evolize MCP server?
Evolize is an MCP server listed in the public MCP registry as com.evolize/accessibility-scanner. Accessibility scans with evidence, public reports, and fresh checks after fixes. This page covers its hosted endpoint (https://evolize.com/api/mcp).
Is the Evolize MCP server safe to use?
Evolize scores 18 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 Evolize MCP server expose?
Evolize exposes 3 tools: get_public_report, scan_website, get_scan_result. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.
Does the Evolize MCP server require authentication?
Its publisher declares no required credentials for Evolize. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Evolize MCP server still maintained?
Evolize is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.