Fiscalité française ouverte, par BENSAID Avocats
REMOTE · OUTILS.BENSAID-AVOCATS.FR
Official French tax texts, dated and sourced: 237 treaty instruments by article, BOFiP, CGI, LPF.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security63
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2094 tokens (~299/item across 7 items; 7 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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://outils.bensaid-avocats.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bensaid-avocats.fr | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1386f10a90b3d57f134935e3fcffe1ca |
| SANs: bensaid-avocats.fr, outils.bensaid-avocats.fr, *.outils.bensaid-avocats.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 outils.bensaid-avocats.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| bensaid-avocats.fr. | No DS | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://outils.bensaid-avocats.fr/mcp | Verified | 200 | |
| http (plaintext) | http://outils.bensaid-avocats.fr/mcp | Served over HTTP | 200 |
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 →
bofip_get Lire un document BOFiP ~208
Texte d'un document BOFiP par identifiant BOI (ex. BOI-RPPM-PVBMI-50-10-10, avec ou sans date), par tranches de 40000 caractères (paramètre `debut`), avec titre, date de publication et permalien officiel bofip.impots.gouv.fr. Source : BOFiP-Impôts, données ouvertes DGFiP, stock et flux appliqués jusqu'au 30/09/2026, licence ouverte Etalab 2.0. / Text of a BOFiP document by BOI id, paged, with publication date and official permalink. DGFiP open data, Etalab 2.0.
| Name | Type | Req | Description |
|---|---|---|---|
| boi | string | yes | Identifiant BOI. / BOI identifier. |
| debut | integer | – | Position de départ dans le texte (pagination par tranches de 40000 caractères ; reprendre la valeur suite.debut). / Start offset for paging. |
No output schema declared.
No examples provided.
bofip_search Rechercher dans la doctrine fiscale (BOFiP) ~238
Recherche sémantique dans le Bulletin officiel des finances publiques (BOFiP-Impôts, doctrine administrative de la DGFiP), versions en vigueur seulement. Rend les BOI classés par pertinence avec extrait, date de publication et permalien officiel ; lire le texte avec bofip_get. Source : BOFiP-Impôts, données ouvertes DGFiP (data.gouv.fr), stock et flux appliqués jusqu'au 30/09/2026, licence ouverte Etalab 2.0. / Semantic search in BOFiP-Impôts (French tax administration guidance), current versions only; returns BOI ids, excerpts and official permalinks. Source: DGFiP open data, Etalab 2.0 open licence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Nombre de résultats (1 à 8, défaut 6). |
| query | string | yes | Question ou sujet. / Question or topic. |
| serie | string | – | Série BOFiP (IR, IS, TVA, RPPM, ENR, PAT, BIC, INT, CF...). / BOFiP series. |
No output schema declared.
No examples provided.
conventions_article Lire un article exact d'une convention fiscale ~394
Texte EXACT d'un article d'une convention fiscale conclue par la France, avec l'intitulé de l'acte, le PDF officiel, les notes d'avenant et les avertissements (acte dénoncé, non en vigueur, texte OCR, avenants à vérifier). Donner `pays` (ou `acte`) et `article` (ex. 18, 1er, 28 bis) ; `objet: successions` pour la convention successorale ; `paragraphe` isole un paragraphe numéroté. Aucune reformulation. Source : conventions publiées sur impots.gouv.fr (PDF officiels), corpus au 2026-10-13, licence ouverte Etalab 2.0. / Exact text of one treaty article (by country or instrument id), with amendment notes and warnings. Source: treaties published on impots.gouv.fr (official PDFs), corpus as of 2026-10-13, Etalab 2.0 open licence.
| Name | Type | Req | Description |
|---|---|---|---|
| acte | string | – | Identifiant d'acte (prioritaire sur pays). / Instrument id (overrides country). |
| article | string | yes | Numéro d'article : 18, 1er, 28 bis. / Article number. |
| objet | string | – | revenu (défaut) ou successions, donations... / Subject (default: income). |
| paragraphe | string | – | Numéro de paragraphe (optionnel). / Paragraph number. |
| partie | string | – | protocole, echange... (par défaut le corps de l'acte). / Part of the instrument. |
| pays | string | – | Pays en français ou en anglais, ou code ISO à 3 lettres (Suisse, Royaume-Uni, United States, ITA). / Country name in French or English, or ISO alpha-3 code. |
No output schema declared.
No examples provided.
conventions_get Lire le texte intégral d'un acte conventionnel ~229
Texte intégral d'un acte (convention, avenant, protocole) par son identifiant `acte` (conv-N, rendu par conventions_search), avec le lien du PDF officiel. Texte long : rendu par tranches de 40000 caractères (paramètre `debut`). Pour un seul article, préférer conventions_article. Source : conventions publiées sur impots.gouv.fr (PDF officiels), corpus au 2026-10-13, licence ouverte Etalab 2.0. / Full text of a treaty instrument by id (conv-N), paged, with the official PDF link. Source: treaties published on impots.gouv.fr (official PDFs), corpus as of 2026-10-13, Etalab 2.0 open licence.
| Name | Type | Req | Description |
|---|---|---|---|
| acte | string | yes | Identifiant de l'acte, ex. conv-214. / Instrument id. |
| debut | integer | – | Position de départ dans le texte (pagination par tranches de 40000 caractères ; reprendre la valeur suite.debut). / Start offset for paging. |
No output schema declared.
No examples provided.
conventions_search Rechercher dans les conventions fiscales de la France ~337
Recherche sémantique, article par article, dans les 237 actes des conventions fiscales conclues par la France (126 pays : conventions, avenants, protocoles, accords). Rend les articles pertinents avec numéro, intitulé de l'acte, extrait du texte officiel, lien du PDF et score (seuil 0,40) ; une référence explicite (« article 18 Suisse ») est résolue directement. Préciser `pays` quand il est connu. Lire ensuite l'article avec conventions_article. Source : conventions publiées sur impots.gouv.fr (PDF officiels), corpus au 2026-10-13, licence ouverte Etalab 2.0. / Semantic article-level search across France's 237 tax treaty instruments (126 countries). Returns article number, instrument title, official text excerpt, PDF link and score; no generated answer. Source: treaties published on impots.gouv.fr (official PDFs), corpus as of 2026-10-13, Etalab 2.0 open licence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Nombre de résultats (1 à 8, défaut 6). |
| objet | string | – | Nature de l'acte (revenu par défaut pour la recherche : tous). / Instrument subject. |
| pays | string | – | Pays en français ou en anglais, ou code ISO à 3 lettres (Suisse, Royaume-Uni, United States, ITA). / Country name in French or English, or ISO alpha-3 code. |
| query | string | yes | Question ou sujet, en français de préférence. / Question or topic. |
No output schema declared.
No examples provided.
legifrance_article Lire un article du CGI ou du LPF (Légifrance) ~223
Texte en vigueur d'un article du Code général des impôts (cgi) ou du Livre des procédures fiscales (lpf), par son numéro (ex. 150-0 B ter, 757 B, L. 64), avec l'identifiant LEGIARTI, la date d'entrée en vigueur et le lien Légifrance. Source : Légifrance (DILA) via l'API PISTE, licence ouverte Etalab 2.0, consulté à la date de l'appel ; mis en cache 24 h. / In-force text of a French General Tax Code (cgi) or Tax Procedure Book (lpf) article by number, from Légifrance (DILA) through the PISTE API, Etalab 2.0 open licence; cached 24 h.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | yes | Numéro d'article : 150-0 B ter, 757 B, L. 64. / Article number. |
| code | string | yes | cgi ou lpf. |
No output schema declared.
No examples provided.
openfisca_parameter Lire un barème ou un taux de la législation (OpenFisca) ~254
Valeur d'un paramètre de la législation socio-fiscale française (barèmes, taux, plafonds) tel que codé dans OpenFisca France, à une date donnée (aujourd'hui par défaut), avec les dernières valeurs datées et leurs références légales. Ex. impot_revenu.bareme_ir_depuis_1945.bareme, taxation_capital.pfu.taux. Un chemin partiel rend la liste des paramètres correspondants. Source : API publique OpenFisca France (api.fr.openfisca.org), mise en cache 24 h ; vérifier sur le texte officiel. / Value of a French tax-benefit legislation parameter (scales, rates, ceilings) from the public OpenFisca France API, at a given date, with dated history and legal references; cached 24 h.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date de valeur AAAA-MM-JJ (défaut : aujourd'hui). / Value date. |
| historique | integer | – | Nombre de valeurs datées rendues (défaut 5). / Number of dated values. |
| name | string | yes | Chemin du paramètre (points ou barres obliques). / Parameter path. |
No output schema declared.
No examples provided.
How do I install the Fiscalité française ouverte, par BENSAID Avocats MCP server?
Fiscalité française ouverte, par BENSAID Avocats is a hosted endpoint at https://outils.bensaid-avocats.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 · outils.bensaid-avocats.fr
claude mcp add --transport http fr-bensaid-avocats-fiscalite 'https://outils.bensaid-avocats.fr/mcp'
What is the Fiscalité française ouverte, par BENSAID Avocats MCP server?
Fiscalité française ouverte, par BENSAID Avocats is an MCP server listed in the public MCP registry as fr.bensaid-avocats/fiscalite. Official French tax texts, dated and sourced: 237 treaty instruments by article, BOFiP, CGI, LPF. This page covers its hosted endpoint (https://outils.bensaid-avocats.fr/mcp).
Is the Fiscalité française ouverte, par BENSAID Avocats MCP server safe to use?
Fiscalité française ouverte, par BENSAID Avocats 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 Fiscalité française ouverte, par BENSAID Avocats MCP server expose?
Fiscalité française ouverte, par BENSAID Avocats exposes 7 tools: conventions_search, conventions_get, conventions_article, bofip_search, bofip_get, and 2 more. Their descriptions and schemas cost roughly 1,883 tokens of context every time the server is loaded.
Does the Fiscalité française ouverte, par BENSAID Avocats MCP server require authentication?
No. We connected to Fiscalité française ouverte, par BENSAID Avocats without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fiscalité française ouverte, par BENSAID Avocats MCP server still maintained?
Fiscalité française ouverte, par BENSAID Avocats 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 Fiscalité française ouverte, par BENSAID Avocats MCP server?
VerifyMCP ran 13 checks on Fiscalité française ouverte, par BENSAID Avocats, 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.