40trust / 100
Validatethat MCP
by validatethat.io in News & content
MCP serverFailing, checked 35 h ago
Run UX research from Claude — create card sort studies, list studies, pull headline stats.
https://validatethat.io/mcp- Tools
- -
- behind sign-in or payment
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 35 h ago, next in 41 h
Reliability
All checks passedSome failedAll failedNot checked
Latest check failed 35 h ago: initialize returned HTTP 405
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers. It asks for sign-in, an API key or payment.
{
"mcpServers": {
"validatethat-mcp": {
"type": "http",
"url": "https://validatethat.io/mcp"
}
}
}The tool list is behind sign-in or payment, so we can't show it.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 35 h ago | initialize returned HTTP 405 | 405 | 194 ms |
| 4 days ago | initialize returned HTTP 405 | 405 | 191 ms |
| 8 days ago | initialize returned HTTP 405 | 405 | 271 ms |
| 11 days ago | initialize returned HTTP 405 | 405 | 221 ms |
| 15 days ago | initialize returned HTTP 405 | 405 | 191 ms |
Show 10 older checks
| 18 days ago | initialize returned HTTP 405 | 405 | 262 ms |
| 21 days ago | initialize returned HTTP 405 | 405 | 978 ms |
| 22 days ago | initialize returned HTTP 405 | 405 | 307 ms |
| 23 days ago | initialize returned HTTP 405 | 405 | 179 ms |
| 24 days ago | initialize returned HTTP 405 | 405 | 169 ms |
| 26 days ago | initialize returned HTTP 405 | 405 | 228 ms |
| 27 days ago | initialize returned HTTP 405 | 405 | 423 ms |
| 28 days ago | initialize returned HTTP 307 | 307 | 316 ms |
| 29 days ago | initialize returned HTTP 307 | 307 | 219 ms |
| 30 days ago | initialize returned HTTP 307 | 307 | 76 ms |