Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

rendita

REMOTE · RENDITA.FR

French dividends read in the filings (BALO, AMF): amount, ex-date, payment date, quote. No key.

Available components

+3 this week 76 Trust /100

Last scanned (7 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 511 tokens (~255/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://rendita.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rendita.fr CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA256 42336a9f5dc010fc132b93c3b1d80766
SANs: rendita.fr
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rendita.fr. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
rendita.fr. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rendita.fr/mcp Verified 200
http (plaintext) http://rendita.fr/mcp HTTPS enforced 301 https://rendita.fr/mcp
MCP tools · 2 exposed · ~241 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_french_dividend ~121

The dividend per share one company listed in Paris pays for the current fiscal year: amount, status (confirmed by two registers, announced by one, revised, disputed), nature (interim, final, total, special), ex-date, payment date, the filings that state it with the sentence quoted, and the amounts of earlier fiscal years. Pass an ISIN or a company name; an ambiguous name is refused with the candidates.

NameTypeReqDescription
companystringyesAn ISIN (12 characters) or a company name, in French or as listed.
NameTypeReqDescription
datestringyes–
empreintestringyes–
faitobjectyes–
sourceobjectyes–

No examples provided.

list_french_dividend_dates ~120

The ex-dates and payment dates published by the companies listed in Paris in a window of days starting at a date (today by default, 30 days by default, 120 at most), with the amount per share and its status. Optionally the CAC 40 only.

NameTypeReqDescription
daysinteger–Length of the window. 30 when left out.
fromstring–First day of the window, YYYY-MM-DD. Today when left out.
indexstring–Restrict to the CAC 40.
NameTypeReqDescription
datestringyes–
empreintestringyes–
faitobjectyes–
sourceobjectyes–

No examples provided.

Install

How do I install the rendita MCP server?

rendita is a hosted endpoint at https://rendita.fr/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · rendita.fr

# add to Claude Code
claude mcp add --transport http fr-rendita-rendita 'https://rendita.fr/mcp'
Common questions

What is the rendita MCP server?

rendita is an MCP server listed in the public MCP registry as fr.rendita/rendita. French dividends read in the filings (BALO, AMF): amount, ex-date, payment date, quote. No key. This page covers its hosted endpoint (https://rendita.fr/mcp).

Is the rendita MCP server safe to use?

rendita scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the rendita MCP server expose?

rendita exposes 2 tools: get_french_dividend, list_french_dividend_dates. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.

Does the rendita MCP server require authentication?

No. We connected to rendita without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the rendita MCP server still maintained?

rendita is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.