marlo
Marlo accessibility checker

Marlo developer portal

Use published accessibility measurements through the public API, local CLI, and MCP tools.

Choose the surface for your job

Use the public API to inspect rule coverage, calibration evidence, and routing decisions. Use the local CLI to scan HTML you own and receive findings with engine provenance. The hosted API serves published metadata; it does not accept pages, upload source files, or run remote scans.

Read the API and CLI documentation, download the OpenAPI specification, or read the machine-readable usage guide. Published measurements remain visible on The numbers and their method is described on Method.

Run Marlo without installing it

The playground runs Marlo's own rules in your browser on a web address, a public GitHub repository, or HTML you paste, and offers a bookmarklet that does the same on any page you open. A web address is fetched once by this site, which returns that page's HTML and stores nothing; a repository is read straight from GitHub. They run one engine of the four, so the CLI finds more.

For the full scan without Node.js, use the container image:

docker run --rm -v "$PWD:/work" ghcr.io/karthiksubramanian07/marlo scan page.html

Try the live metadata sandbox

No account, API key, or authorization header is required for these read-only requests. The sandbox is the same public metadata surface used by integrations.

curl -sS 'https://trymarlo.pages.dev/api/v1/coverage'
curl -sS 'https://trymarlo.pages.dev/api/v1/rules'

Read the response before relying on a measurement. Missing evidence, unsupported renderer capabilities, and unimplemented rules are limitations to report, rather than successful accessibility checks.

MCP and source access

The MCP endpoint supports stateless Streamable HTTP for reading coverage, listing rules, and explaining a rule. Its tools are marlo_coverage, marlo_list_rules, and marlo_explain_rule. Discover the endpoint through the MCP manifest.

The source repository contains the CLI, rule implementations, calibration harness, and test corpus. The CLI runs from a source checkout or the container image. A registry release is not required for the public metadata API.