mcpbeat Sign in

thott.bot MCP Server

answering

thott.bot is answering right now. Last checked 13 min ago.

Everything about WoW Forever, in the chat app you already use.

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

Nothing serious here today

Today is the operative word: we check thott.bot 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 13 min ago.

run in your terminal
claude mcp add thott-bot --transport http https://mcp.thott.bot/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.thott.bot/mcp
~/.codex/config.toml
[mcp_servers.thott-bot]
url = "https://mcp.thott.bot/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "thott-bot": {
      "url": "https://mcp.thott.bot/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "thott-bot": {
      "type": "http",
      "url": "https://mcp.thott.bot/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.thott.bot/mcp streamable-http sign-in 246 ms 13 min ago

Alternatives to thott.bot

same job, measured the same way
Polydev
by polydev-ai

Every AI model, inside the app you already use: ask GPT, Claude, Gemini or Grok, and see what paid.

678 installs/wk answering
repofit
by pth2002

Find GitHub projects that fit you, using what your coding agents already know about you.

786 installs/wk local only
NoMac (all tools)
by nomac

Everything NoMac in one server: the Mac, the cloud iPhone and the App Store.

answering
Pacevera
by henryyeh182

Turns the training evidence you already have into a decision about today's session.

local only
Maplith
by maplith

The company brain for your AI agents: how your business works, from the systems you already use.

answering
Chipp
by chipp

Every Chipp tool in one MCP (large). For one area at a time, use the ai.chipp/chipp-* servers.

answering
Owl24 MCP
by madnands5

Hand a production error to the coding agent you already use — it claims it and writes the fix.

54 installs/wk local only
BrowserTap MCP
by linvireo

MCP server that drives the real Chrome you already use, through an extension and CDP.

144 installs/wk local only

thott.bot — questions

Answers built from our own checks of this server.

Why is there no tool list for thott.bot?
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 thott.bot 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 365 ms. The bar chart above shows every period we have measured.
How do I connect thott.bot?
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 thott.bot?
No API key is involved. thott.bot 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 thott.bot?
It answers our handshake in 365 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.