Remote MCP · Endpoint

DER SP: DARE MCP server

No. DER SP: DARE answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_der_sp_dare

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/der_sp_dare-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
7 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
DER SP: DARE, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Listing
From the official MCP registry (active).
Recent checks of DER SP: DARE
CheckedResultHandshake
1 day agoHandshake completed49 ms
3 days agoHandshake completed65 ms
5 days agoHandshake completed82 ms
7 days agoHandshake completed109 ms
8 days agoHandshake completed45 ms
9 days agoHandshake completed143 ms
12 days agoHandshake completed140 ms
13 days agoHandshake completed107 ms
15 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed143 ms
18 days agoHandshake completed65 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed65 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed65 ms
23 days agoHandshake completed67 ms

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

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