Remote MCP · Endpoint

Renda Fixa MCP server

No. Renda Fixa answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://rendafixa.api.br/mcp

The last check completed an MCP handshake.

Registry name
br.api.rendafixa/renda-fixa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
404 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Brazilian fixed income (CDB, LCI, LCA, CRI, CRA, Tesouro) ranked by net-of-tax and real return.
Listing
From the official MCP registry (active).
Recent checks of Renda Fixa
CheckedResultHandshake
2 hours agoHandshake completed404 ms
1 day agoHandshake completed654 ms
2 days agoHandshake completed1.60 s
2 days agoHandshake completed574 ms
4 days agoHandshake completed390 ms
7 days agoHandshake completed682 ms
9 days agoHandshake completed462 ms
12 days agoHandshake completed525 ms
14 days agoHandshake completed505 ms
16 days agoHandshake completed385 ms
18 days agoHandshake completed387 ms
20 days agoHandshake completed386 ms
22 days agoHandshake completed412 ms
23 days agoHandshake completed406 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 Renda Fixa and makes no claim about it beyond what these checks measured.