io.github.parkragsterman/whyismy-org
REMOTE · WHYISMY.ORG · SCANNED SEP 20
Sourced answers to everyday "why is my…" questions — health, pets, home, plumbing, tech, cars.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 619 tokens (~123/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the io.github.parkragsterman/whyismy-org MCP server?
io.github.parkragsterman/whyismy-org is a hosted endpoint at https://whyismy.org/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 · whyismy.org
claude mcp add --transport http parkragsterman-whyismy-org 'https://whyismy.org/mcp'
{
"mcpServers": {
"parkragsterman-whyismy-org": {
"url": "https://whyismy.org/mcp"
}
}
} {
"servers": {
"parkragsterman-whyismy-org": {
"type": "http",
"url": "https://whyismy.org/mcp"
}
}
} [mcp_servers.parkragsterman-whyismy-org] url = "https://whyismy.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"parkragsterman-whyismy-org": {
"type": "remote",
"url": "https://whyismy.org/mcp",
"enabled": true
}
}
} openclaw mcp add parkragsterman-whyismy-org --url 'https://whyismy.org/mcp' --transport streamable-http
mcp_servers:
parkragsterman-whyismy-org:
url: "https://whyismy.org/mcp" {
"McpServers": {
"parkragsterman-whyismy-org": {
"Transport": "http",
"Url": "https://whyismy.org/mcp"
}
}
} assistant mcp add parkragsterman-whyismy-org -t streamable-http -u 'https://whyismy.org/mcp'
{
"mcpServers": {
"parkragsterman-whyismy-org": {
"type": "http",
"url": "https://whyismy.org/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.
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- New tool “list_calculators” functional
- 29 Aug 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- 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
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 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
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 20 Sept 2026 · Probed https://whyismy.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whyismy.org | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 42c4455d71f5c4170ed09ffa5e33f301 |
| SANs: whyismy.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of whyismy.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| whyismy.org. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whyismy.org/mcp | Verified | 200 | |
| http (plaintext) | http://whyismy.org/mcp | HTTPS enforced | 301 | https://whyismy.org/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 →
get_article Read a WhyIsMy.org article ~102
Get the direct answer, the causes the article covers, and its FAQ for one article, by slug (from search_articles). Returns a summary, not the full text — the article URL has the complete step-by-step fix and the sources.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional. If slug is unknown or wrong, the closest match to this text is returned instead. |
| slug | string | – | Article slug, e.g. "why-is-my-phone-on-sos". |
No output schema declared.
No examples provided.
list_calculators Find WhyIsMy.org interactive calculators ~178
Find WhyIsMy.org's free interactive calculators, checkers and estimators (dosage, health, eldercare cost, pet, home and car tools). Both arguments are optional: omit everything to browse, pass query and/or category to narrow. Each result is a one-line teaser plus a link — the calculators are interactive and compute a personalized result client-side in the user's browser, so send the user to the URL for their result instead of estimating it yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category name to filter, e.g. "Health", "Dogs", "Finance", "Cars". |
| limit | integer | – | Max results, 1-25. Default 5. |
| query | string | – | What the user wants to calculate, e.g. "dog benadryl dose" or "medicaid spend down". |
No output schema declared.
No examples provided.
list_topics List WhyIsMy.org topics ~44
List the subject areas covered on WhyIsMy.org with an article count for each. Takes no arguments. Use the returned slugs as the `topic` argument to search_articles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_articles Search WhyIsMy.org articles ~150
Find WhyIsMy.org articles answering a "why is my…" question. Returns titles, summaries and URLs. Both arguments are optional: omit query to browse, pass topic to bias results toward one subject area. The returned summaries are partial — send the user to the article URL for the full diagnosis, fixes and cited sources.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, 1-25. Default 5. |
| query | string | – | What the user is asking, e.g. "phone stuck on SOS" or "why is my dog shaking". |
| topic | string | – | Optional topic slug to bias results (see list_topics), e.g. "health", "dogs", "plumbing". |
No output schema declared.
No examples provided.
What is the io.github.parkragsterman/whyismy-org MCP server?
io.github.parkragsterman/whyismy-org is an MCP server listed in the public MCP registry as io.github.parkragsterman/whyismy-org. Sourced answers to everyday "why is my…" questions, health, pets, home, plumbing, tech, cars. This page covers its hosted endpoint (https://whyismy.org/mcp).
Is the io.github.parkragsterman/whyismy-org MCP server safe to use?
io.github.parkragsterman/whyismy-org scores 87 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.parkragsterman/whyismy-org MCP server expose?
io.github.parkragsterman/whyismy-org exposes 4 tools: search_articles, get_article, list_topics, list_calculators. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.
Does the io.github.parkragsterman/whyismy-org MCP server require authentication?
No. We connected to io.github.parkragsterman/whyismy-org without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.parkragsterman/whyismy-org MCP server still maintained?
io.github.parkragsterman/whyismy-org is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.