Remote MCP · Endpoint

Dueback MCP server

No. Dueback answered an MCP handshake 28 minutes ago.

UpLast checked 28 minutes ago

Server URL

https://api.dueback.co/mcp/

The last check completed an MCP handshake.

Registry name
io.github.dunrossmai-rgb/dueback-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Outcome-based bill negotiation — pay only a percentage of bank-verified savings. Free to try.
Listing
From the official MCP registry (active).
Recent checks of Dueback
CheckedResultHandshake
28 minutes agoHandshake completed294 ms
10 days agoHandshake completed568 ms
11 days agoHandshake completed298 ms
11 days agoHandshake completed300 ms
13 days agoHandshake completed299 ms
14 days agoHandshake completed305 ms
15 days agoHandshake completed304 ms
16 days agoHandshake completed304 ms
17 days agoHandshake completed301 ms
19 days agoHandshake completed299 ms
21 days agoHandshake completed299 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed305 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 Dueback and makes no claim about it beyond what these checks measured.