io.github.sattyamjjain/whycant
REMOTE · WHYCANTWEHAVEANAGENTFORTHIS.COM · SCANNED SEP 22
Roast any AI agent idea from your IDE: verdict tier, readiness score, top risk, shareable URL.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 392 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.sattyamjjain/whycant MCP server?
io.github.sattyamjjain/whycant is a hosted endpoint at https://whycantwehaveanagentforthis.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · whycantwehaveanagentforthis.com
claude mcp add --transport http sattyamjjain-whycant 'https://whycantwehaveanagentforthis.com/api/mcp'
{
"mcpServers": {
"sattyamjjain-whycant": {
"url": "https://whycantwehaveanagentforthis.com/api/mcp"
}
}
} {
"servers": {
"sattyamjjain-whycant": {
"type": "http",
"url": "https://whycantwehaveanagentforthis.com/api/mcp"
}
}
} [mcp_servers.sattyamjjain-whycant] url = "https://whycantwehaveanagentforthis.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sattyamjjain-whycant": {
"type": "remote",
"url": "https://whycantwehaveanagentforthis.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add sattyamjjain-whycant --url 'https://whycantwehaveanagentforthis.com/api/mcp' --transport streamable-http
mcp_servers:
sattyamjjain-whycant:
url: "https://whycantwehaveanagentforthis.com/api/mcp" {
"McpServers": {
"sattyamjjain-whycant": {
"Transport": "http",
"Url": "https://whycantwehaveanagentforthis.com/api/mcp"
}
}
} assistant mcp add sattyamjjain-whycant -t streamable-http -u 'https://whycantwehaveanagentforthis.com/api/mcp'
{
"mcpServers": {
"sattyamjjain-whycant": {
"type": "http",
"url": "https://whycantwehaveanagentforthis.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://whycantwehaveanagentforthis.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whycantwehaveanagentforthis.com | CN=YR1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | RSA 2048 | SHA256-RSA | 6ac3de73a0fd77b9cb9a42041011aaaa804 |
| SANs: whycantwehaveanagentforthis.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of whycantwehaveanagentforthis.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| whycantwehaveanagentforthis.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; style-src-elem 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whycantwehaveanagentforthis.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://whycantwehaveanagentforthis.com/api/mcp | HTTPS enforced | 308 | https://whycantwehaveanagentforthis.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
browse_explore Browse the public roast corpus ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max 20. Default 10. |
| query | string | – | Free-text filter over name/problem. |
| sort | string | – | Sort order. Default: newest. |
No output schema declared.
No examples provided.
get_stats Public roast-corpus stats ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verdict Look up an existing verdict ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The /result/[id] id or slug returned by a prior roast_idea call. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | yes | – |
| percentileFraming | – | yes | "You're the X% who…" line |
| readinessBand | string | yes | Letter band A-F |
| readinessScore | number | yes | Agent-readiness 0-100 |
| resultUrl | string | yes | Canonical /result/[id] share URL |
| savageLine | string | yes | – |
| scopeCallUrl | – | yes | Cal.com 20-min scope-call URL |
| topRiskCode | – | yes | Top OWASP-MCP risk code, e.g. MCP-3 |
| topRiskTitle | – | yes | – |
| verdict | string | yes | Real VerdictTier enum value, e.g. SHUT_UP_AND_TAKE_MY_MONEY |
| verdictLabel | string | yes | – |
No examples provided.
roast_idea Roast an AI agent idea ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idea | string | yes | The agent idea or problem to analyze, in one or two sentences. e.g. "an agent that auto-declines pointless meetings". |
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | yes | – |
| percentileFraming | – | yes | "You're the X% who…" line |
| readinessBand | string | yes | Letter band A-F |
| readinessScore | number | yes | Agent-readiness 0-100 |
| resultUrl | string | yes | Canonical /result/[id] share URL |
| savageLine | string | yes | – |
| scopeCallUrl | – | yes | Cal.com 20-min scope-call URL |
| topRiskCode | – | yes | Top OWASP-MCP risk code, e.g. MCP-3 |
| topRiskTitle | – | yes | – |
| verdict | string | yes | Real VerdictTier enum value, e.g. SHUT_UP_AND_TAKE_MY_MONEY |
| verdictLabel | string | yes | – |
No examples provided.
What is the io.github.sattyamjjain/whycant MCP server?
io.github.sattyamjjain/whycant is an MCP server listed in the public MCP registry as io.github.sattyamjjain/whycant. Roast any AI agent idea from your IDE: verdict tier, readiness score, top risk, shareable URL. This page covers its hosted endpoint (https://whycantwehaveanagentforthis.com/api/mcp).
Is the io.github.sattyamjjain/whycant MCP server safe to use?
io.github.sattyamjjain/whycant scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.sattyamjjain/whycant MCP server expose?
io.github.sattyamjjain/whycant exposes 4 tools: roast_idea, get_verdict, get_stats, browse_explore. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.
Does the io.github.sattyamjjain/whycant MCP server require authentication?
No. We connected to io.github.sattyamjjain/whycant without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.sattyamjjain/whycant MCP server still maintained?
io.github.sattyamjjain/whycant is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.