Evolize
mcp remote · streamable-http · v0.1.0 · source: crawl
https://evolize.com/api/mcp
Accessibility scans with evidence, public reports, and fresh checks after fixes.
Works
100
Verified Oct 31, 2026 · p50 349 ms · p95 666 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'evolize-accessibility-scanner' |
| tools_listed | 15 | pass | 3 tools |
| schema_complete | 15 | pass | 3 of 3 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 349 ms |
| latency_p95 | 5 | pass | p95 666 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (3)
| Name | Description | Schema |
|---|---|---|
get_public_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 sa | typed |
scan_website | 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=tru | typed |
get_scan_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 | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/com-evolize-accessibility-scanner)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.