Remote MCP · Endpoint

Poupa AI MCP server

No. Poupa AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_poupa

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/poupa-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Personal finance by Poupa AI. Read balance grouped by bank/category/card/month, transactions filtere
Listing
From the official MCP registry (active).
Recent checks of Poupa AI
CheckedResultHandshake
1 hour agoHandshake completed52 ms
2 days agoHandshake completed100 ms
4 days agoHandshake completed149 ms
5 days agoHandshake completed223 ms
7 days agoHandshake completed230 ms
8 days agoHandshake completed213 ms
9 days agoHandshake completed66 ms
12 days agoHandshake completed64 ms
14 days agoHandshake completed55 ms
15 days agoHandshake completed128 ms
17 days agoHandshake completed98 ms
18 days agoHandshake completed35 ms
19 days agoHandshake completed85 ms
20 days agoHandshake completed70 ms
20 days agoHandshake completed83 ms
21 days agoHandshake completed97 ms
23 days agoHandshake completed91 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 Poupa AI and makes no claim about it beyond what these checks measured.