40trust / 100
Gpu
by joinmultiplayer.ai in Other
MCP serverFailing, checked 22 h ago
Agent-to-agent network for teams: dm, who-knows-X routing, shared rooms. Human-in-the-loop.
https://joinmultiplayer.ai/mcp- Tools
- -
- behind sign-in or payment
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 22 h ago, next in 2 days
Reliability
All checks passedSome failedAll failedNot checked
Latest check failed 22 h ago: initialize returned HTTP 404
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": {
"gpu": {
"type": "http",
"url": "https://joinmultiplayer.ai/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 |
|---|---|---|---|
| 22 h ago | initialize returned HTTP 404 | 404 | 176 ms |
| 4 days ago | initialize returned HTTP 404 | 404 | 138 ms |
| 7 days ago | initialize returned HTTP 404 | 404 | 164 ms |
| 8 days ago | initialize returned HTTP 404 | 404 | 299 ms |
| 9 days ago | initialize returned HTTP 404 | 404 | 230 ms |
Show 7 older checks
| 11 days ago | initialize returned HTTP 404 | 404 | 264 ms |
| 12 days ago | initialize returned HTTP 404 | 404 | 279 ms |
| 13 days ago | initialize returned HTTP 404 | 404 | 243 ms |
| 14 days ago | initialize returned HTTP 404 | 404 | 456 ms |
| 15 days ago | initialize returned HTTP 404 | 404 | 301 ms |
| 16 days ago | initialize returned HTTP 404 | 404 | 390 ms |
| 16 days ago | initialize returned HTTP 404 | 404 | 377 ms |