Kilotest
REMOTE · KILOTEST.COM · SCANNED SEP 21
Ensemble testing of web pages for accessibility, usability, and standards conformity
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 702 tokens (~87/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · kilotest.com
claude mcp add --transport http jrpool-kilotest 'https://kilotest.com/mcp'
{
"mcpServers": {
"jrpool-kilotest": {
"url": "https://kilotest.com/mcp"
}
}
} {
"servers": {
"jrpool-kilotest": {
"type": "http",
"url": "https://kilotest.com/mcp"
}
}
} [mcp_servers.jrpool-kilotest] url = "https://kilotest.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jrpool-kilotest": {
"type": "remote",
"url": "https://kilotest.com/mcp",
"enabled": true
}
}
} openclaw mcp add jrpool-kilotest --url 'https://kilotest.com/mcp' --transport streamable-http
mcp_servers:
jrpool-kilotest:
url: "https://kilotest.com/mcp" {
"McpServers": {
"jrpool-kilotest": {
"Transport": "http",
"Url": "https://kilotest.com/mcp"
}
}
} assistant mcp add jrpool-kilotest -t streamable-http -u 'https://kilotest.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
- “requestFeature” reworded the description of “feature” cosmetic
- “requestTest” reworded the description of “description” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 20 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://kilotest.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kilotest.com | CN=YE2,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5c044a083a03061390c3bbb72c0d34cdccc |
| SANs: kilotest.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kilotest.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kilotest.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kilotest.com/mcp | Verified | 200 | |
| http (plaintext) | http://kilotest.com/mcp | HTTPS enforced | 308 | https://kilotest.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getReport ~62
Get one full report in JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| jobID | string | yes | Job identifier of the report (example: x9z) |
| timeStamp | string | yes | Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432) |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
listDiagnoses ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| catalogIndex | string | yes | Identifier of the issue-exhibiting element in the catalog of elements on the page (example: 372) |
| issueID | string | yes | Issue identifier (example: contrastPoor) |
| jobID | string | yes | Job identifier of the report (example: x9z) |
| timeStamp | string | yes | Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432) |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
listIssues ~70
Provide details about one report, including basics about the issues reported in it.
| Name | Type | Req | Description |
|---|---|---|---|
| jobID | string | yes | Job identifier of the report (example: x9z) |
| timeStamp | string | yes | Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432) |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
listReports ~15
Provide basics about all available reports.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
listViolators ~97
Provide details about one issue in one report, including basics about the elements of the tested page that were reported as exhibiting the issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issueID | string | yes | Issue identifier (example: contrastPoor) |
| jobID | string | yes | Job identifier of the report (example: x9z) |
| timeStamp | string | yes | Timestamp of the report in YYMMDDTHHmm format (example: 260503T0432) |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
requestFeature ~41
Process my request to add or improve a feature.
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | yes | 20- to 1000-character description of requested feature improvement or new feature |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | null | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
requestRetest ~101
Process my request to retest a page about which a report is available.
| Name | Type | Req | Description |
|---|---|---|---|
| jobID | string | yes | Job identifier of the latest report about the page (example: x9z) |
| reason | string | yes | 20- to 100-character reason why the page should be retested |
| timeStamp | string | yes | Timestamp of the latest report about the page in YYMMDDTHHmm format (example: 260503T0432) |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
requestTest ~101
Process my request to test a page about which no report is available yet.
| Name | Type | Req | Description |
|---|---|---|---|
| URL | string | yes | 12- to 300-character URL of the page, including the https:// scheme and any query |
| description | string | yes | 1- to 100-character description of the page conforming to the naming convention used in the listReports output |
| reason | string | yes | 20- to 100-character reason why the page should be tested |
| Name | Type | Req | Description |
|---|---|---|---|
| URLs of similar requests for web users | – | yes | – |
| response content | object | yes | – |
| response metadata | – | yes | – |
| this request | object | yes | – |
| tool collection | – | yes | – |
| tool name | string | yes | – |
No examples provided.
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.