Remote MCP · Endpoint

EQI MCP MCP server

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

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_eqi

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/eqi-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Connect your EQI account to AI via Brazil's Open Finance: balances, statements, cards, investments.
Listing
From the official MCP registry (active).
Recent checks of EQI MCP
CheckedResultHandshake
1 hour agoHandshake completed134 ms
2 days agoHandshake completed57 ms
4 days agoHandshake completed106 ms
5 days agoHandshake completed219 ms
7 days agoHandshake completed95 ms
8 days agoHandshake completed56 ms
9 days agoHandshake completed162 ms
12 days agoHandshake completed85 ms
14 days agoHandshake completed72 ms
15 days agoHandshake completed94 ms
17 days agoHandshake completed59 ms
18 days agoHandshake completed70 ms
19 days agoHandshake completed51 ms
20 days agoHandshake completed235 ms
20 days agoHandshake completed112 ms
21 days agoHandshake completed105 ms
23 days agoHandshake completed98 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 EQI MCP and makes no claim about it beyond what these checks measured.