Skip to content
Official MCP RegistryListed

Kilotest

Part ofKilotestlisted on 3 directories

Ensemble testing of web pages for accessibility, usability, and standards conformity

First seen 2 Oct 2026. Evidence as of 7 Oct 2026.

12
Tools
From an anonymous probe
1
Source listings
Each with its own history
13
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
awaitTestWait for a job ordered via the orderNewTest or orderRetest tool to complete, using the report identifier either tool returned. Blocks until the report is ready, the job fails, or a maximum wait time elapses; sends no interim notices. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
getKilotestOverviewExplain what Kilotest is, what its tools do, and how its results are structured. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
getReportGet one full report in JSON. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
listDiagnosesProvide details about one element reported as exhibiting one issue in one report, including the diagnoses provided by rule engines about how the element exhibited the issue. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
listIssuesProvide details about one report, including basics about the issues reported in it. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
listReportsProvide basics about all available reports. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
listViolatorsProvide details about one issue in one report, including basics about the elements of the tested page that were reported as exhibiting the issue. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Read-only
orderNewTestProcess my order to test a page about which no report is available yet, immediately and automatically approved, instead of waiting for manual approval. Testing typically takes about 2 minutes and occasionally up to 4 minutes. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Changes data
orderRetestProcess my order to retest a page immediately and automatically approved, instead of waiting for manual approval. Testing typically takes about 2 minutes and occasionally up to 4 minutes. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Changes data
requestFeatureProcess my request to add or improve a feature. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Changes data
requestNewTestProcess my request to test a page about which no report is available yet. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Changes data
requestRetestProcess my request to retest a page about which a report is available. Kilotest tests web pages for front-end quality (accessibility, usability, and standards conformity); results are organized as report, then issue, then violator element, then diagnosis.Changes data

Change history

  1. requestTest: tool removed
  2. requestRetest: input schema changed
  3. requestNewTest: tool added
  4. requestFeature: input schema changed
  5. orderRetest: tool added
  6. orderNewTest: tool added
  7. listViolators: input schema changed
  8. listReports: input schema changed
  9. listIssues: input schema changed
  10. listDiagnoses: input schema changed
  11. getReport: input schema changed
  12. awaitTest: tool added
  13. server instructions changed (+"requestNewTest" +"tested, or the orderNewTest tool for immediate, automatically approved testing." +"retested, or the orderRetest tool for immediate, automatically approved retesting.")
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.jrpool/kilotest2 Oct 20267 Oct 20261