Remote MCP · Endpoint

rendita MCP server

No. rendita answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://rendita.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.rendita/rendita
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
165 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
French dividends read in the filings (BALO, AMF): amount, ex-date, payment date, quote. No key.
Website
https://rendita.fr/api
Listing
From the official MCP registry (active).
Recent checks of rendita
CheckedResultHandshake
35 minutes agoHandshake completed165 ms
9 days agoHandshake completed221 ms
10 days agoHandshake completed229 ms
11 days agoHandshake completed105 ms
12 days agoHandshake completed266 ms
14 days agoHandshake completed202 ms
14 days agoHandshake completed271 ms
15 days agoHandshake completed128 ms
17 days agoHandshake completed498 ms
19 days agoHandshake completed234 ms
21 days agoHandshake completed102 ms
24 days agoHandshake completed243 ms
26 days agoHandshake completed169 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with rendita and makes no claim about it beyond what these checks measured.