Dataroia Data Trust
REMOTE · API.DATAROIA.COM · SCANNED SEP 22
Vérification B2B française : SIRET, SIRENE, dirigeants RNE, santé d'entreprise. Hébergé en France.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1123 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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
claude mcp add --transport http com-dataroia-data-trust 'https://api.dataroia.com/mcp/'
{
"mcpServers": {
"com-dataroia-data-trust": {
"url": "https://api.dataroia.com/mcp/"
}
}
} {
"servers": {
"com-dataroia-data-trust": {
"type": "http",
"url": "https://api.dataroia.com/mcp/"
}
}
} [mcp_servers.com-dataroia-data-trust] url = "https://api.dataroia.com/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dataroia-data-trust": {
"type": "remote",
"url": "https://api.dataroia.com/mcp/",
"enabled": true
}
}
} openclaw mcp add com-dataroia-data-trust --url 'https://api.dataroia.com/mcp/' --transport streamable-http
mcp_servers:
com-dataroia-data-trust:
url: "https://api.dataroia.com/mcp/" {
"McpServers": {
"com-dataroia-data-trust": {
"Transport": "http",
"Url": "https://api.dataroia.com/mcp/"
}
}
} assistant mcp add com-dataroia-data-trust -t streamable-http -u 'https://api.dataroia.com/mcp/'
{
"mcpServers": {
"com-dataroia-data-trust": {
"type": "http",
"url": "https://api.dataroia.com/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
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 22 Sept 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=YE2,O=Let's Encrypt,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 547fbc21b95578a6b0b0decd2441257a163 |
| SANs: api.dataroia.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | present | 19718 | 13 | Verified |
| dataroia.com. | present | 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/ |
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 →
croiser_deces ~124
Croise une liste de contacts avec 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| personnes | array | yes | – |
No output schema declared.
No examples provided.
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
| Name | Type | Req | Description |
|---|---|---|---|
| csv_texte | string | yes | – |
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 (1 SIREN par appel).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| sirens | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entreprises | array | yes | – |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| sirens | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| marquer_lues | boolean | – | – |
| non_lues_seulement | boolean | – | – |
No output schema declared.
No examples provided.
surveillance_portefeuille ~162
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), pas un compteur d'appels.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| api_key | string | yes | – |
| sirens | – | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sirets | array | yes | – |
No output schema declared.
No examples provided.
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 82 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 995 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.