# Kilotest (remote · kilotest.com)

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

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `kilotest.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/jrpool-kilotest/kilotest.md), [page](https://verifymcp.io/servers/jrpool-kilotest/kilotest)

## Channel facts

- Endpoint: `https://kilotest.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.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-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 702 tokens (~87/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Kilotest MCP server?

Kilotest is a hosted endpoint at https://kilotest.com/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 jrpool-kilotest 'https://kilotest.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jrpool-kilotest": {
      "url": "https://kilotest.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jrpool-kilotest": {
      "type": "http",
      "url": "https://kilotest.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jrpool-kilotest]
url = "https://kilotest.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jrpool-kilotest": {
      "type": "remote",
      "url": "https://kilotest.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jrpool-kilotest --url 'https://kilotest.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jrpool-kilotest:
    url: "https://kilotest.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jrpool-kilotest": {
      "Transport": "http",
      "Url": "https://kilotest.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jrpool-kilotest -t streamable-http -u 'https://kilotest.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jrpool-kilotest": {
      "type": "http",
      "url": "https://kilotest.com/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-09-21 (score 84, +1)

- [cosmetic] “requestFeature” reworded the description of “feature”
- [cosmetic] “requestTest” reworded the description of “description”

### 2026-09-20 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `listReports` (~15 tokens)

Provide basics about all available reports.

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `listIssues` (~70 tokens)

Provide details about one report, including basics about the issues reported in it.

Input parameters:

- `jobID` (string, required): Job identifier of the report (example: x9z)
- `timeStamp` (string, required): Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `listViolators` (~97 tokens)

Provide details about one issue in one report, including basics about the elements of the tested page that were reported as exhibiting the issue.

Input parameters:

- `issueID` (string, required): Issue identifier (example: contrastPoor)
- `jobID` (string, required): Job identifier of the report (example: x9z)
- `timeStamp` (string, required): Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `listDiagnoses` (~129 tokens)

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

Input parameters:

- `catalogIndex` (string, required): Identifier of the issue-exhibiting element in the catalog of elements on the page (example: 372)
- `issueID` (string, required): Issue identifier (example: contrastPoor)
- `jobID` (string, required): Job identifier of the report (example: x9z)
- `timeStamp` (string, required): Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `getReport` (~62 tokens)

Get one full report in JSON.

Input parameters:

- `jobID` (string, required): Job identifier of the report (example: x9z)
- `timeStamp` (string, required): Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432)

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `requestTest` (~101 tokens)

Process my request to test a page about which no report is available yet.

Input parameters:

- `URL` (string, required): 12- to 300-character URL of the page, including the https:// scheme and any query
- `description` (string, required): 1- to 100-character description of the page conforming to the naming convention used in the listReports output
- `reason` (string, required): 20- to 100-character reason why the page should be tested

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `requestRetest` (~101 tokens)

Process my request to retest a page about which a report is available.

Input parameters:

- `jobID` (string, required): Job identifier of the latest report about the page (example: x9z)
- `reason` (string, required): 20- to 100-character reason why the page should be retested
- `timeStamp` (string, required): Timestamp of the latest report about the page in YYMMDDTHHmm format (example: 260503T0432)

Output parameters:

- `URLs of similar requests for web users`
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

### `requestFeature` (~41 tokens)

Process my request to add or improve a feature.

Input parameters:

- `feature` (string, required): 20- to 1000-character description of requested feature improvement or new feature

Output parameters:

- `URLs of similar requests for web users` (null)
- `response content` (object)
- `response metadata`
- `this request` (object)
- `tool collection`
- `tool name` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jrpool-kilotest/kilotest#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 73
- 2026-08-29: 73
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71

## Common questions

### What is the Kilotest MCP server?

Kilotest is an MCP server listed in the public MCP registry as io.github.jrpool/kilotest. Ensemble testing of web pages for accessibility, usability, and standards conformity. This page covers its hosted endpoint (https://kilotest.com/mcp).

### Is the Kilotest MCP server safe to use?

Kilotest scores 84 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 Kilotest MCP server expose?

Kilotest exposes 8 tools: listReports, listIssues, listViolators, listDiagnoses, getReport, and 3 more. Their descriptions and schemas cost roughly 616 tokens of context every time the server is loaded.

### Does the Kilotest MCP server require authentication?

No. We connected to Kilotest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Kilotest MCP server still maintained?

Kilotest is still listed as active in the MCP registry. We last reached this channel on 21 September 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://kilotest.com/mcp
- Repository: https://github.com/jrpool/kilotest
- Website: https://kilotest.com/
- Changelog RSS feed: https://verifymcp.io/servers/jrpool-kilotest/kilotest.xml
- Changelog JSON feed: https://verifymcp.io/servers/jrpool-kilotest/kilotest.json
- HTML version of this page: https://verifymcp.io/servers/jrpool-kilotest/kilotest