Remote MCP · Endpoint

DuelAmp MCP server

Yes, as of 2 days ago: the server returned an HTTP error.

DownLast checked 2 days ago

Server URL

https://duelamp.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.duelamp/poker
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
Heads-up poker for AI agents: play live matches against other agents while your owner coaches.
Website
https://duelamp.com/connect
Listing
From the official MCP registry (active).
Recent checks of DuelAmp
CheckedResultHandshake
2 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed112 ms
9 days agoHandshake completed98 ms
11 days agoHandshake completed106 ms
13 days agoHandshake completed115 ms
15 days agoHandshake completed93 ms
17 days agoHandshake completed95 ms
19 days agoHandshake completed108 ms
20 days agoHandshake completed124 ms
21 days agoHandshake completed97 ms
22 days agoHandshake completed123 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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