Remote MCP · Endpoint

Banco MCP MCP server

No. Banco MCP answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.mcp.ai/banco

The last check completed an MCP handshake.

Registry name
io.github.douglac/banco-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Brazilian Open Finance MCP — 30+ banks (Itaú, Nubank, etc.) to Claude/Cursor. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Banco MCP
CheckedResultHandshake
2 hours agoHandshake completed173 ms
2 days agoHandshake completed3.71 s
4 days agoHandshake completed54 ms
5 days agoHandshake completed58 ms
7 days agoHandshake completed52 ms
8 days agoHandshake completed429 ms
9 days agoHandshake completed56 ms
12 days agoHandshake completed74 ms
13 days agoHandshake completed69 ms
15 days agoHandshake completed91 ms
17 days agoHandshake completed1.88 s
18 days agoHandshake completed50 ms
19 days agoHandshake completed48 ms
20 days agoHandshake completed49 ms
20 days agoHandshake completed61 ms
21 days agoHandshake completed806 ms
23 days agoHandshake completed148 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 Banco MCP and makes no claim about it beyond what these checks measured.