Remote MCP · Endpoint

The Durability Curve MCP server

No. The Durability Curve answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
317 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 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
6 hours agoHandshake completed317 ms
3 days agoHandshake completed390 ms
12 days agoHandshake completed290 ms
13 days agoHandshake completed381 ms
14 days agoHandshake completed304 ms
15 days agoHandshake completed520 ms
16 days agoHandshake completed315 ms
17 days agoHandshake completed226 ms
18 days agoHandshake completed261 ms
20 days agoHandshake completed422 ms
22 days agoHandshake completed153 ms
25 days agoHandshake completed311 ms
27 days agoHandshake completed397 ms
29 days agoHandshake completed235 ms

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

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.