io.github.parkragsterman/whyismy-org
REMOTE · WHYISMY.ORG · SCANNED AUG 3
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 →
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 Usability85
- 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
- Tool/resource definitions use about 399 tokens (~99/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · whyismy.org
claude mcp add --transport http parkragsterman-whyismy-org 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- 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 70
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 3 Aug 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 | 7 Jul 2026 | 5 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 49882d5bf0b19f1513f996c12bd91063 |
| 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 |
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 |
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.
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_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.