sh.knowngood/knowngood

https://knowngood.sh/mcp

Search agent-ready sites or fetch one site's report; every capability probe-verified, dated.

55
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Aug 27Aug 29Aug 31Sep 2

Response time

p50 100ms · p95 170ms
0ms 100ms 200ms Aug 27Aug 29Aug 31Sep 2
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/27/2026, 12:00:00 AM 100% 12 89ms
8/28/2026, 12:00:00 AM 100% 21 95ms
8/29/2026, 12:00:00 AM 100% 21 93ms
8/30/2026, 12:00:00 AM 100% 20 108ms
8/31/2026, 12:00:00 AM 100% 21 120ms
9/1/2026, 12:00:00 AM 100% 21 96ms
9/2/2026, 12:00:00 AM 100% 11 128ms
55
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
not yet measured

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
—
Networks
—
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
—
Domain registered
—
Hosting network
CLOUDFLARENET
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

Response schema 
{
  "type": "object"
}