# Evolize (remote · evolize.com)

Accessibility scans with evidence, public reports, and fresh checks after fixes.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- remote · `evolize.com`: 18/100 (this document), [markdown](https://verifymcp.io/servers/com-evolize-accessibility-scanner/api-mcp.md), [page](https://verifymcp.io/servers/com-evolize-accessibility-scanner/api-mcp)

## Channel facts

- Endpoint: `https://evolize.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-19.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-evolize-accessibility-scanner 'https://evolize.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-evolize-accessibility-scanner": {
      "url": "https://evolize.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-evolize-accessibility-scanner": {
      "type": "http",
      "url": "https://evolize.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-evolize-accessibility-scanner]
url = "https://evolize.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-evolize-accessibility-scanner": {
      "type": "remote",
      "url": "https://evolize.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-evolize-accessibility-scanner --url 'https://evolize.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-evolize-accessibility-scanner:
    url: "https://evolize.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-evolize-accessibility-scanner": {
      "Transport": "http",
      "Url": "https://evolize.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-evolize-accessibility-scanner -t streamable-http -u 'https://evolize.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-evolize-accessibility-scanner": {
      "type": "http",
      "url": "https://evolize.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 18, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.10 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-15 (score 67, +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.

### 2026-10-14 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-13 (score 66)

First indexed and scored.

## MCP tools (3)

### `get_public_report` (~197 tokens)

Get an existing public accessibility report

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.

Input parameters:

- `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, required): The public website to assess, e.g. `example.com` or `https://example.com`. Not an Evolize URL.

### `scan_website` (~208 tokens)

Request an accessibility assessment

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.

Input parameters:

- `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, required): The public website to assess, e.g. `example.com` or `https://example.com`. Not an Evolize URL.

### `get_scan_result` (~143 tokens)

Read an assessment result

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.

Input parameters:

- `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, required): The opaque handle returned by scan_website.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-evolize-accessibility-scanner/api-mcp#diagnostics

## Score history

- 2026-10-19: 18
- 2026-10-18: 18
- 2026-10-17: 18
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 66
- 2026-10-13: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://evolize.com/api/mcp
- Website: https://evolize.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-evolize-accessibility-scanner/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-evolize-accessibility-scanner/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-evolize-accessibility-scanner/api-mcp