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.

Dataroia Data Trust

REMOTE · API.DATAROIA.COM

Vérification B2B française : SIRET, SIRENE, dirigeants RNE, santé d'entreprise. Hébergé en France.

Available components

0 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

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 Security77
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1127 tokens (~140/item across 8 items; 8 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 Management86
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 13 Nov 26 −3
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.28.1 ▼ security
    • Tool “croiser_deces” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “dirigeants_entreprise” rewrote its description, which is the text the model reads security
    • Tool “surveillance_portefeuille” rewrote its description, which is the text the model reads security
    • New tool “verifier_deces” functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “croiser_deces” rewrote its description, which is the text the model reads security
    • Tool “sante_entreprise” rewrote its description, which is the text the model reads security
    • Tool “surveillance_portefeuille” rewrote its description, which is the text the model reads security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 21 Nov 2026 · Probed https://api.dataroia.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.dataroia.com CN=YE1,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA384 5008126cee651651183c8b4ece836bfbeb8
SANs: api.dataroia.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.dataroia.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dataroia.com. DS published 61736 8 Verified
api.dataroia.com. Verified address RRset verified with the apex keys
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://api.dataroia.com/mcp/ Verified 200
http (plaintext) http://api.dataroia.com/mcp/ HTTPS enforced 301 https://api.dataroia.com/mcp/
MCP tools · 8 exposed · ~1,000 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
diagnostiquer_echantillon ~137

Diagnostic qualité gratuit d'un extrait de fichier CRM/client au format CSV (max 100 lignes, en-tête inclus) : emails et téléphones invalides, SIREN/SIRET à clé fausse, doublons, cellules vides, identifiants détruits par Excel. Aucun envoi à un tiers, aucun stockage. Pour le diagnostic complet gratuit (1000 lignes, croisement SIRENE/BODACC/décès + manque à gagner chiffré) : https://dataroia.com

NameTypeReqDescription
csv_textestringyes–

No output schema declared.

No examples provided.

dirigeants_entreprise ~84

Dirigeants actifs au RNE (INPI) pour une liste de SIREN, croisés avec le registre INSEE décès (statut vital + score). Clé API requise — le plan gratuit y a accès (5 SIREN par appel).

NameTypeReqDescription
api_keystringyes–
sirensarrayyes–

No output schema declared.

No examples provided.

resoudre_siren ~163

Retrouve le SIREN d'entreprises françaises à partir de leur nom, tel qu'écrit dans un CRM (formes juridiques et accents ignorés). Fournir le code postal quand il est connu : il départage les homonymes. Jusqu'à 10 entreprises par appel : {"nom": str, "code_postal": str?, "ref": str?}. Réponse par entreprise : siren, denomination officielle, statut, score et fiabilite (sur | probable | ambigu | non_trouve) + candidats alternatifs. Ne jamais écrire un SIREN "ambigu" dans un CRM sans validation humaine. Gratuit, sans clé API.

NameTypeReqDescription
entreprisesarrayyes–

No output schema declared.

No examples provided.

sante_entreprise ~101

Score santé consolidé (0-100, label A-D) par SIREN : statut SIRENE, procédures BODACC, comptes annuels INPI, benchmark Banque de France, dirigeants RNE croisés avec le registre INSEE décès. Clé API requise — le plan gratuit y a accès (5 SIREN par appel).

NameTypeReqDescription
api_keystringyes–
sirensarrayyes–

No output schema declared.

No examples provided.

surveillance_alertes ~133

Alertes détectées sur le portefeuille surveillé : cessation SIRENE, nouvelle procédure collective BODACC, changement ou décès de dirigeant. C'est l'outil « quoi de neuf depuis mon dernier passage » — inutile de re-vérifier les SIREN un par un. marquer_lues=true acquitte les alertes retournées (le prochain appel ne rendra que les nouveautés). Clé API requise.

NameTypeReqDescription
api_keystringyes–
marquer_luesboolean––
non_lues_seulementboolean––

No output schema declared.

No examples provided.

surveillance_portefeuille ~168

Gère le portefeuille de SIREN surveillés par Dataroia (cessations, procédures collectives BODACC, changements et décès de dirigeants). action : "lister" | "ajouter" | "retirer" — sirens requis sauf lister. Le premier passage sur un SIREN établit une référence silencieuse ; les changements suivants deviennent des alertes (voir surveillance_alertes). Clé API requise ; la limite est la taille du portefeuille par plan (free 10, solo 50, starter 100, business 1000, enterprise illimité), pas un compteur d'appels.

NameTypeReqDescription
actionstringyes–
api_keystringyes–
sirens–––

No output schema declared.

No examples provided.

verifier_deces ~123

Vérifie une liste de contacts dans le registre INSEE des décès. Chaque personne : {"nom": str, "prenom": str, "annee_naissance": int?, "date_naissance": "YYYY-MM-DD"?, "code_postal": str?, "ref": str?}. Résultat prudent : les correspondances non certaines sont marquées « à vérifier (homonyme) ». Accessible dès le plan gratuit, dans la limite de son quota.

NameTypeReqDescription
api_keystringyes–
personnesarrayyes–

No output schema declared.

No examples provided.

verifier_siret ~91

Vérifie jusqu'à 10 SIRET (14 chiffres) sur la base SIRENE INSEE locale : existence, établissement fermé, unité légale cessée, procédure collective BODACC. Si l'établissement est fermé, indique le SIRET successeur quand un lien de succession SIRENE existe. Gratuit, sans clé API.

NameTypeReqDescription
siretsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the Dataroia Data Trust MCP server?

Dataroia Data Trust is a hosted endpoint at https://api.dataroia.com/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 · api.dataroia.com

# add to Claude Code
claude mcp add --transport http com-dataroia-data-trust 'https://api.dataroia.com/mcp/'
Common questions

What is the Dataroia Data Trust MCP server?

Dataroia Data Trust is an MCP server listed in the public MCP registry as com.dataroia/data-trust. Vérification B2B française : SIRET, SIRENE, dirigeants RNE, santé d'entreprise. Hébergé en France. This page covers its hosted endpoint (https://api.dataroia.com/mcp/).

Is the Dataroia Data Trust MCP server safe to use?

Dataroia Data Trust scores 79 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 Dataroia Data Trust MCP server expose?

Dataroia Data Trust exposes 8 tools: verifier_siret, diagnostiquer_echantillon, resoudre_siren, sante_entreprise, dirigeants_entreprise, and 3 more. Their descriptions and schemas cost roughly 1,000 tokens of context every time the server is loaded.

Does the Dataroia Data Trust MCP server require authentication?

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

Is the Dataroia Data Trust MCP server still maintained?

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

What did VerifyMCP test on the Dataroia Data Trust MCP server?

VerifyMCP ran 13 checks on Dataroia Data Trust, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.