# Jrpool Kilotest MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.jrpool%2Fkilotest
Registry id: `mcp-registry/io.github.jrpool/kilotest`
Status: live (checked 2026-10-27T06:05:22.449Z)

## Verdict

Jrpool Kilotest MCP server answered 99.94% of Glimind's liveness checks over 30 days, better than 33% of MCP servers, with 382 ms median handshake and 4 outages in 90 days. Its agent-readiness grade is A (97/100) across 12 tools, costing an agent about 2,222 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.94% | 33% of MCP servers |
| Median handshake latency | 382 ms | 55% of MCP servers |
| p95 handshake latency | 2649 ms | — |
| Checks in 30 days | 5,030 | — |
| Outages, 90 days | 4 | — |
| Median recovery | 5 min | — |
| Agent-readiness score | 97/100 (A) | 90% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~2,222 tokens | 51% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

```sh
claude mcp add --transport http jrpool-kilotest-mcp-server https://kilotest.com/mcp
```

## Tools (12)

- `awaitTest`: Waits for a job ordered via the orderNewTest or orderRetest tool to finish, using the report identifier either tool returned. Use this instead of polling listIs
- `getKilotestOverview`: Explains what Kilotest is, what its tools do, and how its results are structured. Use this before any other tool when the available tools or workflow are unclea
- `getReport`: Retrieves one entire report as JSON, with all of its issues, violators, and diagnoses. Use this instead of drilling down through listIssues, listViolators, and 
- `listDiagnoses`: Lists the diagnoses that rule engines gave for how one element exhibited one issue in one report. Use this after listViolators to get details about the element 
- `listIssues`: Lists the issues reported in one report, along with the history of all reports about the same page. Use this after listPages to switch to an earlier or later re
- `listPages`: Lists all pages Kilotest has tested. Use this first to discover whether a page already has any reports before requesting a test. Returns, for each tested page, 
- `listViolators`: Lists the elements of a tested page that were reported as exhibiting one issue in one report. Use this after listIssues to drill down from an issue to the eleme
- `orderNewTest`: Orders testing of a page that has no report yet, with automated approval or rejection and immediate enqueueing if approved. Use this instead of requestNewTest w
- `orderRetest`: Orders a retest of a page whose existing report is considered obsolete, with automated approval or rejection and immediate enqueuing if approved. Use this inste
- `requestFeature`: Submits a request to add a new feature or improve an existing one; queued for manager review. There is no immediate-approval alternative for feature requests. R
- `requestNewTest`: Submits a request to test a page that has no report yet; queued for manager approval. Use orderNewTest instead for immediate, automatically approved testing. Re
- `requestRetest`: Submits a request to retest a page whose existing report is considered obsolete; queued for manager approval. Use orderRetest instead for immediate, automatical

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.