mcpbeat Sign in

TestWatch MCP Server

by testwatch Your server? Claim it
answering

TestWatch is answering right now. Last checked 7 min ago.

Run your end-to-end tests, read why they failed, write new tests. Sign in with OAuth.

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
177 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check TestWatch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add testwatch --transport http https://mcp.testwatch.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.testwatch.dev/mcp
~/.codex/config.toml
[mcp_servers.testwatch]
url = "https://mcp.testwatch.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "testwatch": {
      "url": "https://mcp.testwatch.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "testwatch": {
      "type": "http",
      "url": "https://mcp.testwatch.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.testwatch.dev/mcp streamable-http sign-in 210 ms 7 min ago

Alternatives to TestWatch

same job, measured the same way
Lettrove
by lettrove

Design emails from a brief, send tests, send to your lists now or scheduled, and read delivery.

answering
tinyprobe
by kikutano

API testing in YAML: inspect, call and run endpoints and workflows, with the guide to write them.

local only
Mida
by mida

Create, run and analyze A/B tests and personalizations on your site with Mida.

answering
Kurlo
by kurlo

Run, write and test the API requests saved in a Kurlo workspace, the open source API client.

947 installs/wk local only
Vinv
by vinvai

Vinv runs, tests, and finds issues in your services — with zero code changes.

74 installs/wk local only
Idea Launch
by idea-launch

Validate SaaS and app ideas with real, managed ad tests from your coding agent.

answering
Optux
by optux

Create and run A/B tests, patches, split tests and feature flags on your website

answering
Proxy Mail QA
by proxymail

Test inboxes for your app's sign-up and login emails: get the code or link, or why none came.

answering

TestWatch — questions

Answers built from our own checks of this server.

Why is there no tool list for TestWatch?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is TestWatch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 177 ms. The bar chart above shows every period we have measured.
How do I connect TestWatch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to TestWatch?
No API key is involved. TestWatch answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is TestWatch?
It answers our handshake in 177 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.