Remote MCP · Endpoint

Asaas MCP server

No. Asaas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_asaas

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/asaas-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
7 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Digital account and billing on Asaas with the full official REST API v3 (api.asaas.com), balance, ch
Listing
From the official MCP registry (active).
Recent checks of Asaas
CheckedResultHandshake
1 hour agoHandshake completed67 ms
2 days agoHandshake completed5.01 s
4 days agoHandshake completed63 ms
5 days agoHandshake completed136 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed211 ms
9 days agoHandshake completed55 ms
12 days agoHandshake completed78 ms
13 days agoHandshake completed45 ms
15 days agoHandshake completed1.27 s
16 days agoHandshake completed69 ms
18 days agoHandshake completed63 ms
19 days agoHandshake completed40 ms
19 days agoFailed - the request timed out—
20 days agoHandshake completed40 ms
21 days agoHandshake completed3.02 s
23 days agoHandshake completed148 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 Asaas and makes no claim about it beyond what these checks measured.