99tests
REMOTE · 99TESTS.COM
Order human-run real-device app tests from your coding agent; verified bugs return as fix prompts.
Available components
Last scanned (6 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 236 tokens (~47/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +8
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol version: 2024-11-05 → 2025-06-18 functional
- Tool “create_test_job” changed its title: Create test job cosmetic
- Tool “get_job_status” changed its title: Get job status cosmetic
- Tool “get_report” changed its title: Get verified report cosmetic
- Tool “get_sample_report” changed its title: Get sample report cosmetic
- Tool “list_packages” changed its title: List packages cosmetic
- 4 Nov 26 65
First indexed and scored.
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 5 Nov 2026 · Probed https://99tests.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=99tests.com | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3b5b7d2178c8d7470e36cb9e4caf57d8 |
| SANs: 99tests.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of 99tests.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 99tests.com. | present | 13642, 16675 | 13, 13 | Verified |
| 99tests.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://99tests.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://99tests.com/api/mcp | HTTPS enforced | 301 | https://99tests.com/api/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 →
create_test_job Create test job ~79
Create a 99tests test job and return a hosted checkout link to pay in a browser. Never charges a card directly.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO country code for currency |
| string | yes | Customer email for the invoice, status link and report | |
| package | string | yes | One of: starter, standard, deep |
No output schema declared.
No examples provided.
get_job_status Get job status ~48
Check a job's stage and progress using the customer's own status link or token. Poll at most every 10 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| status_token | string | yes | The customer's status link or its token |
No output schema declared.
No examples provided.
get_report Get verified report ~48
Get the verified findings for a delivered job as ready-to-paste fix prompts, using the customer's own status link or token.
| Name | Type | Req | Description |
|---|---|---|---|
| status_token | string | yes | The customer's status link or its token |
No output schema declared.
No examples provided.
get_sample_report Get sample report ~31
Get a description and link to an example 99tests report, so you can see the format before paying.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_packages List packages ~30
List 99tests packages, prices (INR + GST and USD), session counts, devices and turnaround.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the 99tests MCP server?
99tests is a hosted endpoint at https://99tests.com/api/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 · 99tests.com
claude mcp add --transport http com-99tests-mcp 'https://99tests.com/api/mcp'
What is the 99tests MCP server?
99tests is an MCP server listed in the public MCP registry as com.99tests/mcp. Order human-run real-device app tests from your coding agent; verified bugs return as fix prompts. This page covers its hosted endpoint (https://99tests.com/api/mcp).
Is the 99tests MCP server safe to use?
99tests scores 73 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 99tests MCP server expose?
99tests exposes 5 tools: list_packages, create_test_job, get_job_status, get_report, get_sample_report. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.
Does the 99tests MCP server require authentication?
No. We connected to 99tests without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 99tests MCP server still maintained?
99tests is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.