Remote MCP · Endpoint

DiscreteRate MCP server

No. DiscreteRate answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://discreterate.com/mcp/v1

The last check completed an MCP handshake.

Registry name
com.discreterate/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
28 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Run DRS demos (Fast-Slow Drain, Hamburger Duo, Valdez Tanker) and explore the paradigm.
Listing
From the official MCP registry (active).
Recent checks of DiscreteRate
CheckedResultHandshake
1 hour agoHandshake completed28 ms
2 days agoHandshake completed3.63 s
4 days agoHandshake completed36 ms
5 days agoHandshake completed30 ms
7 days agoHandshake completed41 ms
8 days agoHandshake completed3.93 s
9 days agoHandshake completed34 ms
12 days agoHandshake completed47 ms
13 days agoHandshake completed59 ms
15 days agoHandshake completed3.40 s
16 days agoHandshake completed57 ms
17 days agoHandshake completed35 ms
18 days agoHandshake completed3.12 s
19 days agoHandshake completed56 ms
20 days agoHandshake completed63 ms
21 days agoHandshake completed32 ms
22 days agoHandshake completed50 ms

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

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 DiscreteRate and makes no claim about it beyond what these checks measured.