Remote MCP · Endpoint

ASA MCP MCP server

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

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_asa

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/asa-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
25 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Connect your ASA account to AI via Brazil's Open Finance: balances, statements, cards, investments.
Listing
From the official MCP registry (active).
Recent checks of ASA MCP
CheckedResultHandshake
1 hour agoHandshake completed147 ms
2 days agoHandshake completed122 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed102 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed192 ms
9 days agoHandshake completed67 ms
12 days agoHandshake completed162 ms
13 days agoHandshake completed33 ms
15 days agoHandshake completed4.16 s
16 days agoHandshake completed30 ms
18 days agoHandshake completed67 ms
19 days agoHandshake completed36 ms
19 days agoFailed - the request timed out—
20 days agoHandshake completed61 ms
21 days agoHandshake completed3.37 s
23 days agoHandshake completed372 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 ASA MCP and makes no claim about it beyond what these checks measured.