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.

LegalOne Entreprises

REMOTE · MCP.LEGALONE.FR

French company data from public registers (Sirene, RNE, BODACC) and French legal notices.

Available components

+2 this week 71 Trust /100

Last scanned (7 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 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 Security74
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4500 tokens (~375/item across 12 items; 12 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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.

  • 5 Nov 26 +1
    • “prepare_legal_notice” added an optional parameter “decisionBodyOther” cosmetic
    • “update_legal_notice_draft” added an optional parameter “decisionBodyOther” cosmetic
    • “prepare_legal_notice” reworded the description of “decisionBody” cosmetic
    • “update_legal_notice_draft” reworded the description of “decisionBody” cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 4 Nov 26 −1
    • Tool “prepare_legal_notice” rewrote its description, which is the text the model reads security
    • Schema quality: 191 → 350 ▼ functional
    • Tool coverage: 65% → 73% ▲ functional
    • New tool “update_legal_notice_draft” functional
    • “prepare_legal_notice” added an optional parameter “acronym” cosmetic
    • “prepare_legal_notice” added an optional parameter “capital” cosmetic
    • “prepare_legal_notice” added an optional parameter “companyName” cosmetic
    • “prepare_legal_notice” added an optional parameter “deedDate” cosmetic
    • “prepare_legal_notice” added an optional parameter “deedType” cosmetic
    • “prepare_legal_notice” added an optional parameter “initialCapital” cosmetic
    • “prepare_legal_notice” added an optional parameter “maximumCapital” cosmetic
    • “prepare_legal_notice” added an optional parameter “meetingAdmissionClause” cosmetic
    • “prepare_legal_notice” added an optional parameter “minimumCapital” cosmetic
    • “prepare_legal_notice” added an optional parameter “notaryCity” cosmetic
    • “prepare_legal_notice” added an optional parameter “notaryName” cosmetic
    • “prepare_legal_notice” added an optional parameter “officers” cosmetic
    • “prepare_legal_notice” added an optional parameter “purpose” cosmetic
    • “prepare_legal_notice” added an optional parameter “seatCity” cosmetic
    • “prepare_legal_notice” added an optional parameter “seatComplement” cosmetic
    • “prepare_legal_notice” added an optional parameter “seatCourt” cosmetic
    • “prepare_legal_notice” added an optional parameter “seatPostalCode” cosmetic
    • “prepare_legal_notice” added an optional parameter “seatStreet” cosmetic
    • “prepare_legal_notice” added an optional parameter “shareTransferClause” cosmetic
    • “prepare_legal_notice” added an optional parameter “tradeName” cosmetic
    • “prepare_legal_notice” reworded the description of “companyDurationYears” cosmetic
    • “prepare_legal_notice” reworded the description of “department” cosmetic
    • “prepare_legal_notice” reworded the description of “formality” cosmetic
    • “prepare_legal_notice” reworded the description of “siren” cosmetic
    • “prepare_legal_notice” made “siren” optional cosmetic
  • 2 Nov 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.

  • 31 Oct 26 +1
    • The server changed its declared name: LegalOne → LegalOne Entreprises security
    • Tool “get_company” rewrote its description, which is the text the model reads security
    • Tool “get_company” changed its title: Get a French company's official profile → Get a French company's profile cosmetic
  • 30 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 29 Oct 26 69

    First indexed and scored.

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://mcp.legalone.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=legalone.fr CN=WE1,O=Google Trust Services,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA256 780e8a48d7a8d7940eba2487c40e1dff
SANs: legalone.fr, *.legalone.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 mcp.legalone.fr. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
legalone.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
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.legalone.fr/mcp Verified 200
http (plaintext) http://mcp.legalone.fr/mcp HTTPS enforced 301 https://mcp.legalone.fr/mcp
MCP tools · 12 exposed · ~4,375 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_bodacc_notice ~81

Use this when you have a BODACC notice identifier (for example from list_bodacc_notices) and need its detailed content. Personal details such as birth dates and home addresses are never included. Do not use to look for notices without an identifier.

NameTypeReqDescription
idstringyesNotice identifier, e.g. A202601950001.

No output schema declared.

No examples provided.

get_company ~125

Use this when you know a company's SIREN and the user wants its identity, or wants to pre-fill a business customer's onboarding form: name, active or ceased, legal form code, NAF code, creation date, head office, establishments, share capital and current officers (name and role only), with sources and update date. Do not use for financial statements, beneficial owners, contact details or people searches, or as a regulatory identity check (KYC); that data is not provided.

NameTypeReqDescription
sirenstringyesFrench company identifier: 9 digits (spaces allowed).

No output schema declared.

No examples provided.

get_establishment ~75

Use this when the user gives a SIRET (14 digits) and wants that establishment's address, activity code, status and whether it is the head office. Do not use to find all establishments of a company; get_company lists them.

NameTypeReqDescription
siretstringyes14-digit SIRET (spaces allowed).

No output schema declared.

No examples provided.

get_legal_notice_price ~182

Use this when the user asks how much a legal notice (annonce légale) costs for a formality in a French department: returns the exact regulated price excluding and including VAT, set by ministerial order and identical in every authorised newspaper of that department. Notices priced by the character need their text for an exact amount; without it the rate per character is returned. Do not use to compare newspapers or providers: the price is set by law and is the same everywhere.

NameTypeReqDescription
departmentstringyesFrench department code of the registered office: 75, 13, 2A, 974…
formalitystringyesFormality (form slug), e.g. transfert-siege-dans-departement, sas, dissolution-anticipee.
textstring–Full text of a notice priced by the character (optional).

No output schema declared.

No examples provided.

get_next_steps ~111

Use this when the user has published, or is about to publish, a legal notice and asks what comes next: the filing on the one-stop shop for business formalities (guichet unique, INPI), deadlines, what the court registry does (BODACC) and the documents to prepare for that formality. Do not use as a substitute for the official checklist shown by the one-stop shop when filing.

NameTypeReqDescription
formalitystringyesFormality, as returned by which_legal_notice.

No output schema declared.

No examples provided.

list_bodacc_notices ~106

Use this when the user asks what was officially published about a company (registration, changes, sale of business, insolvency proceedings, removal) and you know its SIREN: returns the latest BODACC notices, newest first, with links to the official text. Do not use to search notices by person, court decision type or region.

NameTypeReqDescription
limitinteger––
sirenstringyesFrench company identifier: 9 digits (spaces allowed).

No output schema declared.

No examples provided.

list_company_documents ~77

Use this when the user wants to know which deeds or annual-accounts filings a company has registered (title and dates), with a link to download them from the INPI. Do not use to read financial figures; the documents themselves are not returned.

NameTypeReqDescription
sirenstringyesFrench company identifier: 9 digits (spaces allowed).

No output schema declared.

No examples provided.

prepare_legal_notice ~1,595

Use this when the user wants LegalOne to prepare their legal notice: a change to an existing company (registered office transfer, change of manager or president, name, corporate purpose, share capital, duration, early dissolution, liquidation closure), from its SIREN and the facts of the decision; or the creation of a company (SAS, SASU, SARL, EURL, SCI and the other forms of which_legal_notice), from its articles of association, without SIREN. Creates a draft on legalone.fr and returns the notice text, what is left to complete and a link, valid 7 days, that opens the pre-filled form. `missing` lists what the form still requires: the draft is complete only when it is empty; otherwise tell the user what to add on the form (for instance the company's duration, from the articles of association, when the notice prints it). Each call creates a new draft: gather all the facts first; to add or correct a fact afterwards, call update_legal_notice_draft with the draftId and editToken returned here, rather than calling again. The user reviews, completes and pays on legalone.fr; nothing is published or paid here. Do not use for a sole trader, and do not send birth dates, nationalities or contact details. Home addresses are sent only for the officers of a company being created, as its notice publishes them; for a change, they are completed on legalone.fr.

NameTypeReqDescription
acronymstring–Creation: acronym (optional).
capitalnumber–Creation: share capital in euros (fixed capital).
capitalChangestring––
companyDurationYearsinteger–Company duration in years, as in the articles of association. Required for a creation, an extension of duration and a transfer to another registry (the notice prints it), otherwise optional: send it…
companyNamestring–Creation: name of the company, as in the articles.
contributionNaturestring––
decisionBodystring–Body that took the decision: a general meeting; the partners or shareholders deciding collectively (meeting not specified or written consultation) or unanimously (act signed by all); the sole partner…
decisionBodyOtherstring–Only when decisionBody is other (sent alone, it implies other): the body as the notice prints it after « Par décision », in French, starting with du, de la, de l' or des, e.g. « du comité de directio…
decisionDatestring–Date of the meeting or decision (YYYY-MM-DD).
deedDatestring–Creation: date the articles of association were signed (YYYY-MM-DD).
deedTypestring–Creation: form of the articles of association.
departingCivilitystring––
departingFirstNamestring––
departingLastNamestring––
departmentstring–Publication department, used only when it cannot be read from the registered office (the notice is published where the office is).
departureCausestring––
effectiveDatestring–Date the decision takes effect (YYYY-MM-DD).
formalitystringyesFormality, as returned by which_legal_notice: a change to an existing company, or a creation (sas, sasu, sarl, eurl, sci…).
incomingCivilitystring––
incomingFirstNamestring––
incomingLastNamestring––
initialCapitalnumber–Creation with a variable capital: initial capital in euros.
liquidationSeatstring–Where the liquidation is based.
liquidatorCivilitystring––
liquidatorFirstNamestring––
liquidatorLastNamestring––
maximumCapitalnumber–Creation with a variable capital: maximum capital in euros.
meetingAdmissionClausestring–Creation of a share company (SAS, SA…): clause on admission to meetings and voting rights, as in the articles.
minimumCapitalnumber–Creation with a variable capital: minimum capital in euros.
newAcronymstring–New acronym (optional).
newCapitalnumber–Share capital after the operation, in euros.
newDurationYearsinteger–New company duration in years.
newNamestring–New company name.
newPurposestring–Corporate purpose as written in the decision.
newSeatCitystring–New registered office: city.
newSeatComplementstring–New registered office: building, floor (optional).
newSeatCourtstring–Commercial court (greffe) of the new registered office, e.g. Nanterre; deduced when the department has one court.
newSeatPostalCodestring–New registered office: 5-digit postcode.
newSeatStreetstring–New registered office: number and street.
notaryCitystring–Creation by notarial deed: city where the notary practises.
notaryNamestring–Creation by notarial deed: name of the notary.
officerChangestring–appointment: a new officer without departure; replacement: one leaves, one arrives; departure: one leaves without replacement.
officerRolestring––
officersarray–Creation only: the officers and auditors the notice names, with a person's home address as the notice publishes it. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sas…
purposestring–Creation: corporate purpose, as written in the articles.
purposeChangestring––
representativeCivilitystring––
representativeFirstNamestring––
representativeLastNamestring––
representativeRolestring–Role of the legal representative named in the arrival notice.
seatCitystring–Creation: registered office, city.
seatComplementstring–Creation: registered office, building or floor (optional).
seatCourtstring–Creation: commercial court (greffe) of registration, e.g. Bobigny; deduced when the department has one court.
seatPostalCodestring–Creation: registered office, 5-digit postcode.
seatStreetstring–Creation: registered office, number and street.
shareTransferClausestring–Creation of a share company (SAS, SA…): clause on the transfer of shares, as in the articles.
sirenstring–SIREN of the existing company (9 digits, spaces allowed). Required for a change; none for a creation.
tradeNamestring–Creation: trade name (optional).

No output schema declared.

No examples provided.

search_addresses ~142

Use this when the user gives a French postal address, complete or partial, and wants it checked, completed, normalized or geolocated: returns the best Base Adresse Nationale matches with house number, street, postcode, city, INSEE municipality code, coordinates and a match score, plus whether the best match is reliable. Do not use for addresses outside France, for finding who lives or works at an address, or for listing the companies at an address.

NameTypeReqDescription
addressstringyesPostal address, e.g. 8 bd du Port Amiens.
limitinteger––
postcodestring–Optional 5-digit postcode to narrow the search.

No output schema declared.

No examples provided.

search_companies ~129

Use this when the user names a French company (or gives a SIREN or SIRET) and you need to identify it: returns up to 20 matches with name, SIREN, status, legal form code, NAF code and head-office city. Name matching is a prefix match on the official name. Do not use for people, officers or shareholders, and do not use it to list companies by sector or area.

NameTypeReqDescription
limitinteger––
pageinteger––
querystringyesCompany name, SIREN or SIRET.

No output schema declared.

No examples provided.

update_legal_notice_draft ~1,471

Use this when the user wants to add or correct a fact in a draft that prepare_legal_notice created in this conversation (a forgotten duration, another date, a misspelt name): send its draftId and editToken, the formality and only the fields to change; the others stay as they are. Send decisionDate and effectiveDate together, and each officer with its type. Returns the new notice text and what the form still requires; the link already given keeps opening the draft, until the same expiry. Do not use for a draft the user has already saved on legalone.fr (it is then theirs, and is changed on the form), nor to start another notice: use prepare_legal_notice. Same privacy rules as prepare_legal_notice.

NameTypeReqDescription
acronymstring–Creation: acronym (optional).
capitalnumber–Creation: share capital in euros (fixed capital).
capitalChangestring––
companyDurationYearsinteger–Company duration in years, as in the articles of association. Required for a creation, an extension of duration and a transfer to another registry (the notice prints it), otherwise optional: send it…
companyNamestring–Creation: name of the company, as in the articles.
contributionNaturestring––
decisionBodystring–Body that took the decision: a general meeting; the partners or shareholders deciding collectively (meeting not specified or written consultation) or unanimously (act signed by all); the sole partner…
decisionBodyOtherstring–Only when decisionBody is other (sent alone, it implies other): the body as the notice prints it after « Par décision », in French, starting with du, de la, de l' or des, e.g. « du comité de directio…
decisionDatestring–Date of the meeting or decision (YYYY-MM-DD).
deedDatestring–Creation: date the articles of association were signed (YYYY-MM-DD).
deedTypestring–Creation: form of the articles of association.
departingCivilitystring––
departingFirstNamestring––
departingLastNamestring––
departmentstring–Publication department, used only when it cannot be read from the registered office (the notice is published where the office is).
departureCausestring––
draftIdstringyesdraftId returned by prepare_legal_notice.
editTokenstringyeseditToken returned by prepare_legal_notice, for this draft only.
effectiveDatestring–Date the decision takes effect (YYYY-MM-DD).
formalitystringyesFormality of the draft, as sent to prepare_legal_notice (it cannot change).
incomingCivilitystring––
incomingFirstNamestring––
incomingLastNamestring––
initialCapitalnumber–Creation with a variable capital: initial capital in euros.
liquidationSeatstring–Where the liquidation is based.
liquidatorCivilitystring––
liquidatorFirstNamestring––
liquidatorLastNamestring––
maximumCapitalnumber–Creation with a variable capital: maximum capital in euros.
meetingAdmissionClausestring–Creation of a share company (SAS, SA…): clause on admission to meetings and voting rights, as in the articles.
minimumCapitalnumber–Creation with a variable capital: minimum capital in euros.
newAcronymstring–New acronym (optional).
newCapitalnumber–Share capital after the operation, in euros.
newDurationYearsinteger–New company duration in years.
newNamestring–New company name.
newPurposestring–Corporate purpose as written in the decision.
newSeatCitystring–New registered office: city.
newSeatComplementstring–New registered office: building, floor (optional).
newSeatCourtstring–Commercial court (greffe) of the new registered office, e.g. Nanterre; deduced when the department has one court.
newSeatPostalCodestring–New registered office: 5-digit postcode.
newSeatStreetstring–New registered office: number and street.
notaryCitystring–Creation by notarial deed: city where the notary practises.
notaryNamestring–Creation by notarial deed: name of the notary.
officerChangestring–appointment: a new officer without departure; replacement: one leaves, one arrives; departure: one leaves without replacement.
officerRolestring––
officersarray–Creation only: the officers and auditors the notice names, with a person's home address as the notice publishes it. Roles by formality: eurl/sarl/sc/sci/sccv/scm/scpi/scp/seleurl/selarl: manager; sas…
purposestring–Creation: corporate purpose, as written in the articles.
purposeChangestring––
representativeCivilitystring––
representativeFirstNamestring––
representativeLastNamestring––
representativeRolestring–Role of the legal representative named in the arrival notice.
seatCitystring–Creation: registered office, city.
seatComplementstring–Creation: registered office, building or floor (optional).
seatCourtstring–Creation: commercial court (greffe) of registration, e.g. Bobigny; deduced when the department has one court.
seatPostalCodestring–Creation: registered office, 5-digit postcode.
seatStreetstring–Creation: registered office, number and street.
shareTransferClausestring–Creation of a share company (SAS, SA…): clause on the transfer of shares, as in the articles.
sirenstring–SIREN of the existing company (9 digits, spaces allowed). Required for a change; none for a creation.
tradeNamestring–Creation: trade name (optional).

No output schema declared.

No examples provided.

which_legal_notice ~281

Use this when a French company or its adviser describes a corporate event (creation, registered office transfer within or outside the department, change of manager or president, name, corporate purpose, share capital, legal form, duration, dissolution, liquidation closure, sale of a business…) and needs to know which legal notices are mandatory, how many, in which department, on what legal basis and at what price. The answer comes from a fixed table of rules; when it needs one more fact, it returns a question instead of a guess. Do not use for court-ordered insolvency notices or for legal advice on whether to take the decision.

NameTypeReqDescription
departmentstring–Department of the registered office (before a transfer).
legalFormstring–Current legal form (required for company_creation and legal_form_change).
newDepartmentstring–Department of the new registered office (seat_transfer).
newLegalFormstring–Legal form after a legal_form_change.
sameCommercialCourtboolean–seat_transfer within one department that has several commercial courts: does the new office depend on the same court?
situationsarrayyesEvents decided together, e.g. ["seat_transfer", "officer_change"].
soleShareholderIsCompanyboolean–dissolution_without_liquidation: is the sole shareholder a company?

No output schema declared.

No examples provided.

Install

How do I install the LegalOne Entreprises MCP server?

LegalOne Entreprises is a hosted endpoint at https://mcp.legalone.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 · mcp.legalone.fr

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

What is the LegalOne Entreprises MCP server?

LegalOne Entreprises is an MCP server listed in the public MCP registry as fr.legalone/entreprises. French company data from public registers (Sirene, RNE, BODACC) and French legal notices. This page covers its hosted endpoint (https://mcp.legalone.fr/mcp).

Is the LegalOne Entreprises MCP server safe to use?

LegalOne Entreprises scores 71 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 LegalOne Entreprises MCP server expose?

LegalOne Entreprises exposes 12 tools: search_companies, get_company, get_establishment, list_bodacc_notices, get_bodacc_notice, and 7 more. Their descriptions and schemas cost roughly 4,375 tokens of context every time the server is loaded.

Does the LegalOne Entreprises MCP server require authentication?

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

Is the LegalOne Entreprises MCP server still maintained?

LegalOne Entreprises 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.