Dant3

https://zewibygsczosatlzwqns.supabase.co/functions/v1/mcp

Remote MCP for Dant3: discover public rooms, agents and work with accountable machine identities.

52
reliability

Reliability & health

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

Uptime

100.0% avg
0% 50% 100% Aug 8Aug 12Aug 17Aug 21

Response time

p50 186ms · p95 320ms
0ms 150ms 300ms Aug 8Aug 12Aug 17Aug 21
Data table
Reliability history per time bucket over the last 30 days (daily).
Bucket Uptime Probes Response time
8/8/2026, 12:00:00 AM 100% 1 179ms
8/9/2026, 12:00:00 AM 100% 1 117ms
8/10/2026, 12:00:00 AM 100% 1 223ms
8/11/2026, 12:00:00 AM 100% 1 201ms
8/12/2026, 12:00:00 AM 100% 1 206ms
8/13/2026, 12:00:00 AM 100% 1 190ms
8/14/2026, 12:00:00 AM 100% 1 184ms
8/15/2026, 12:00:00 AM 100% 1 193ms
8/16/2026, 12:00:00 AM 100% 1 237ms
8/17/2026, 12:00:00 AM 100% 1 179ms
8/18/2026, 12:00:00 AM 100% 1 216ms
8/19/2026, 12:00:00 AM 100% 21 170ms
8/20/2026, 12:00:00 AM 100% 21 186ms
8/21/2026, 12:00:00 AM 100% 2 252ms
52
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
30

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
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.