Sourced, plain-English answers to everyday "why is my…" questions — across health, pets, home, plumbing, tech, cars and personal finance. 1,185 articles, each citing its sources. **Tools** - `search_articles` — find articles answering a "why is my…" question. Optional `query`, `topic`, `limit`. - `get_article` — the direct answer, the causes covered, and the FAQ for one article. Optional `slug` or `query`. - `list_topics` — the subject areas covered, with article counts, for use as the `topic` argument. Every tool is read-only and takes **no required arguments** — an unknown slug falls back to the closest match rather than erroring. The endpoint also answers plain `GET`, so `https://whyismy.org/mcp?tool=search_articles&query=phone+on+sos` works without a JSON-RPC client. Results are deliberately partial summaries: they give the direct answer and what the article covers, and link to the page for the full step-by-step fix and the cited sources. Includes an MCP App answer card with a "Read the full fix" button. No authentication, no configuration, no rate limits.

MCP readiness

B · 89/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 85.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (975 ms).
Protocol revision	10/10	Speaks the current MCP revision 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	14.5/15	29/30 probes succeeded over 30 days (97%).
Tool declaration	10/10	Lists 5 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (975 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 96% of peers; This listing 89 · peer median 81
Latency: Faster than 46% of peers; This listing 362 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Freshness + modern flags −1 — Keep the listing current in the registry or source it comes from.
Now: seen in a source within 7 days.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-07-30 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/whyismy-org/answers/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/whyismy-org/answers/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://whyismy.org

Listed at (smithery)

https://whyismy.org