mcpbeat

Whycant MCP Server

io.github.sattyamjjain/whycant
not responding

Whycant is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Roast any AI agent idea from your IDE: verdict tier, readiness score, top risk, shareable URL.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 91 checks
4
Tools
read from the server
104 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add whycant --transport http https://whycantwehaveanagentforthis.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "whycant": {
      "url": "https://whycantwehaveanagentforthis.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.whycant]
url = "https://whycantwehaveanagentforthis.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "whycant": {
      "url": "https://whycantwehaveanagentforthis.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "whycant": {
      "url": "https://whycantwehaveanagentforthis.com/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

browse
browse_explore
Page through existing public roasts (the /explore feed) with their shareable /result URLs. Optional free-text query and sort (newest | top | money). Read-only, no rate-limit cost — use it to see whether an idea was already roasted before minting a new one.
roast
roast_idea
Get the full whycantwehaveanagentforthis.com roast for an AI agent idea: the verdict tier, an agent-readiness score (0-100 + band), the top OWASP-MCP security risk, the "you're the X% who…" framing, and a shareable /result URL. Every call mints a real, persistent result page (its own OG share card) — so roasting from your IDE also publishes it. Anonymous (no token): 3/hour, 10/day. Add a token for higher limits.
stats
get_stats
Live public numbers for whycantwehaveanagentforthis.com: total ideas roasted, live results, % told to ship, % that already exist, roast battles, and how many roasts came in via MCP. Read-only, no rate-limit cost.
verdict
get_verdict
Fetch a verdict that was already minted, by its result id or slug. Read-only — no new analysis, no rate-limit cost. Returns the same structured verdict shape as roast_idea.

Endpoints

URLTransportStateLatencyChecked
https://whycantwehaveanagentforthis.com/api/mcp streamable-http answering 104 ms 12 min ago

Whycant — questions

Answers built from our own checks of this server.

What can Whycant do?
It exposes 4 tools, read directly from the server on our last check. Among them: browse_explore, get_stats, get_verdict, roast_idea. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Whycant 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 104 ms. The bar chart above shows every period we have measured.
Is Whycant still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Whycant 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 Whycant?
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 Whycant need an API key?
No. Whycant completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.