Remote MCP · Endpoint

The Durability Curve MCP server

No. The Durability Curve answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.durabilitycurve.com/mcp

The last check completed an MCP handshake.

Registry name
com.durabilitycurve/archive
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
422 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Essays, claim ledgers, weekly calls and laws, plus AI model release dates, prices and free plans.
Listing
From the official MCP registry (active).
Recent checks of The Durability Curve
CheckedResultHandshake
1 hour agoHandshake completed422 ms
2 days agoHandshake completed153 ms
5 days agoHandshake completed311 ms
7 days agoHandshake completed397 ms
9 days agoHandshake completed235 ms
11 days agoHandshake completed363 ms
13 days agoHandshake completed213 ms
15 days agoHandshake completed56 ms
18 days agoHandshake completed179 ms
19 days agoHandshake completed210 ms
20 days agoHandshake completed194 ms
22 days agoHandshake completed478 ms
23 days agoHandshake completed309 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with The Durability Curve and makes no claim about it beyond what these checks measured.