Remote MCP · Endpoint

Rede MCP server

No. Rede answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.mcp.ai/p_rede

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/rede-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Sales, receivables, statements and fees for your own Rede (Brazilian card acquirer) merchant account
Listing
From the official MCP registry (active).
Recent checks of Rede
CheckedResultHandshake
3 hours agoHandshake completed84 ms
2 days agoHandshake completed168 ms
4 days agoHandshake completed62 ms
5 days agoHandshake completed46 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed57 ms
9 days agoHandshake completed312 ms
12 days agoHandshake completed2.17 s
13 days agoHandshake completed6.37 s
15 days agoHandshake completed156 ms
16 days agoHandshake completed65 ms
17 days agoHandshake completed87 ms
18 days agoHandshake completed64 ms
19 days agoHandshake completed63 ms
20 days agoHandshake completed90 ms
21 days agoHandshake completed254 ms
22 days agoHandshake completed205 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 Rede and makes no claim about it beyond what these checks measured.