Remote MCP · Endpoint

XP MCP MCP server

No. XP MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_xp

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/xp-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Connect your XP account to AI via Brazil's Open Finance: balances, statements, cards, investments. R
Listing
From the official MCP registry (active).
Recent checks of XP MCP
CheckedResultHandshake
1 hour agoHandshake completed94 ms
2 days agoHandshake completed286 ms
4 days agoHandshake completed56 ms
5 days agoHandshake completed44 ms
7 days agoHandshake completed163 ms
8 days agoHandshake completed50 ms
9 days agoHandshake completed42 ms
12 days agoHandshake completed90 ms
14 days agoHandshake completed54 ms
15 days agoHandshake completed1.06 s
17 days agoHandshake completed85 ms
18 days agoHandshake completed186 ms
19 days agoHandshake completed66 ms
20 days agoHandshake completed124 ms
21 days agoHandshake completed72 ms
21 days agoHandshake completed72 ms
23 days agoHandshake completed239 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 XP MCP and makes no claim about it beyond what these checks measured.