mcpbeat

Tools MCP Server

net.nymbo/tools
not responding

Tools is listed as active in the registry but did not answer our last check.

Remote MCP server: fetch, search, Python, TTS, memory, image, video.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
100 ms
Response time
average over 24h
open, no key
Access
sse

Connect this server

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

run in your terminal
claude mcp add tools --transport http https://mcp.nymbo.net/gradio_api/mcp/sse
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "tools": {
      "url": "https://mcp.nymbo.net/gradio_api/mcp/sse"
    }
  }
}
~/.codex/config.toml
[mcp_servers.tools]
url = "https://mcp.nymbo.net/gradio_api/mcp/sse"
.cursor/mcp.json
{
  "mcpServers": {
    "tools": {
      "url": "https://mcp.nymbo.net/gradio_api/mcp/sse"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "tools": {
      "url": "https://mcp.nymbo.net/gradio_api/mcp/sse"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://mcp.nymbo.net/gradio_api/mcp/sse sse answering 100 ms 13 min ago

Tools — questions

Answers built from our own checks of this server.

Is Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 100 ms. The bar chart above shows every period we have measured.
The registry lists Tools as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Tools?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tools need an API key?
No. Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.