Remote MCP · Endpoint

Next MCP MCP server

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

UpLast checked 2 hours ago

Server URL

https://api.mcp.ai/p_next

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/next-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.44 s
Tools exposed
25 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Connect your Next account to AI via Brazil's Open Finance: balances, statements, cards, investments.
Listing
From the official MCP registry (active).
Recent checks of Next MCP
CheckedResultHandshake
2 hours agoHandshake completed1.44 s
2 days agoHandshake completed60 ms
4 days agoHandshake completed54 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed69 ms
9 days agoHandshake completed897 ms
12 days agoHandshake completed84 ms
14 days agoHandshake completed61 ms
15 days agoHandshake completed1.57 s
17 days agoHandshake completed74 ms
18 days agoHandshake completed78 ms
19 days agoHandshake completed386 ms
20 days agoHandshake completed94 ms
20 days agoHandshake completed53 ms
21 days agoHandshake completed1.72 s
23 days agoHandshake completed87 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 Next MCP and makes no claim about it beyond what these checks measured.