Remote MCP · Endpoint

Benefits City MCP server

No. Benefits City answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aiagentscity.com/benefits/mcp

The last check completed an MCP handshake.

Registry name
io.github.entradox/benefits-city
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
169 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
US bank, savings and credit-card signup bonuses, each source-checked, with expiry dates.
Listing
From the official MCP registry (active).
Recent checks of Benefits City
CheckedResultHandshake
1 hour agoHandshake completed169 ms
2 days agoHandshake completed148 ms
5 days agoHandshake completed138 ms
7 days agoHandshake completed219 ms
9 days agoHandshake completed289 ms
11 days agoHandshake completed156 ms
13 days agoHandshake completed185 ms
15 days agoHandshake completed175 ms
17 days agoHandshake completed166 ms
19 days agoHandshake completed171 ms
20 days agoHandshake completed185 ms
21 days agoHandshake completed170 ms
23 days agoHandshake completed197 ms
25 days agoHandshake completed163 ms

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

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