mcpbeat Sign in

Whatcha MCP Server

by whatareyoudo Your server? Claim it
answering

Whatcha is answering right now. Last checked 3 min ago.

Read and write in your Whatcha diaries, including exchange diaries shared with a partner.

Uptime history 22 days of history · worst day 99%
22 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
794 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Whatcha missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 3 min ago.

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

Alternatives to Whatcha

same job, measured the same way
WitWiki
by witwiki

A shared team wiki your coding agents read and write — across every repo and every MCP client.

answering
Reef
by reefwith

Shared, living memory for you and your people — coves your AI assistant can read and write.

answering
Wunel
by wunel

Write and edit shared markdown pages with your team; every block shows who wrote it.

answering
currencylayer MCP by usefulapi
by usefulapi

Read and calculate currency exchange rates with your paid currencylayer account.

5 tools answering
Archboard
by getarchboard

Create, read and edit architecture, flow and ER diagrams on a live canvas shared with your team.

answering
TestWatch
by testwatch

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

answering
Comparand
by comparand

Crypto chart past cases: same coin, same exchange shape search with what followed each match.

answering
Notion
by foreverworks

Search, read and write your Notion workspaces, with pages as Markdown and typed database queries.

384 installs/wk local only

Whatcha — questions

Answers built from our own checks of this server.

Why is there no tool list for Whatcha?
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 Whatcha 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 794 ms. The bar chart above shows every period we have measured.
How do I connect Whatcha?
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 Whatcha?
No API key is involved. Whatcha 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 Whatcha?
It answers our handshake in 794 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.