Skip to main content
Glama
deenesfrjakoruzh
yoanbernabeu

MCP Recherche d'entreprises

by yoanbernabeu
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

MCP Business Search

This MCP (API Connection Module) allows you to interact with the Business Search API provided by data.gouv.fr.

Description

The Business Search API allows you to search and find French companies. It offers two types of searches:

  • Text search (name, address, leaders and elected officials)

  • Geographic search

Related MCP server: MCP INPI

Features

The MCP allows you to:

  • Search for companies by different criteria

  • Filter results by multiple parameters

  • Access essential company information (name, SIREN, SIRET, NAF code)

  • Perform geographic searches around a point with the following parameters:

    • Latitude and longitude of the search point

    • Search radius (up to 50km)

    • Activity filters (NAF code, activity section)

    • Results pagination

Source

This MCP is based on the official data.gouv.fr API: Business Search API

Limitations

The API has some limitations:

  • Does not provide access to predecessors and successors of an establishment

  • Does not allow access to non-disseminable companies

  • Does not allow access to companies that have been refused registration with the RCS

  • The geographic search radius is limited to a maximum of 50km

Technical limitations

  • Limit of 7 calls per second

  • Availability: 100% over the last month

  • Access: Open to all

Use

As a user

The easiest way to use this MCP is via npx :

npx mcp-recherche-entreprises

As a developer

  1. Installing dependencies:

npm install

  1. Project build:

npm run build

This command will:

  • Compile TypeScript files to JavaScript

  • Place them in the dist/ folder

  • Make JavaScript files executable

  1. Startup :

To launch the server in development mode with the MCP Inspector (recommended for development):

npm run dev

To launch the server without the Inspector:

npm start

The MCP Inspector provides a graphical interface for testing and debugging MCP requests in real time.

Use with Cursor

To use this MCP in Cursor, add the following configuration to your .cursor/settings.json file:

{
  "mcpServers": {
    "recherche-entreprises": {
      "command": "npx mcp-recherche-entreprises"
    }
  }
}

This configuration will allow Cursor to automatically use this MCP for business searches.

MCP Resources for Contributors

Official documentation

Development tools

Best practices

  • Use the TypeScript SDK for implementation

  • Follow project code conventions

  • Implement robust error handling

  • Clearly document the API

  • Maintain compatibility with future versions

Testing and debugging

  • Using the Inspector for Debugging

  • Implement unit tests

  • Check compliance with the MCP specification

  • Analyze performance with the appropriate tools

License

This project is licensed under the MIT License. See the LICENSE file for details.

Contribution

Contributions are welcome! Check out our contribution guide for more information on how to contribute to this project.

Available Tools

2 tools
rechercher_entrepriseC

Recherche des entreprises françaises selon de nombreux critères (nom, activité, localisation, etc.).

ParametersJSON Schema
NameRequiredDescriptionDefault
qYesTermes de la recherche (dénomination et/ou adresse, dirigeants, élus)
activite_principaleNoLe code NAF ou code APE, un code d'activité suivant la nomenclature de l'INSEE. Ce paramètre accepte une valeur unique ou une liste de valeurs séparées par des virgules. Il ne s'applique qu'à l'unité légale, et non à ses établissements.
section_activite_principaleNoSection de l'activité principale (A à U) selon la nomenclature NAF.
categorie_entrepriseNoCatégorie d'entreprise de l'unité légale (PME, ETI, GE).
nature_juridiqueNoCatégorie juridique de l'unité légale (code INSEE).
etat_administratifNoÉtat administratif de l'entreprise (A: Active, C: Cessée).
tranche_effectif_salarieNoTranche d'effectif salarié de l'entreprise (ex : 10-19, 20-49, etc.).
code_postalNoCode postal en 5 chiffres. Ce paramètre filtre sur les établissements et accepte une valeur unique ou une liste de valeurs séparées par des virgules.
code_communeNoCode commune INSEE en 5 caractères. Ce paramètre filtre sur les établissements et accepte une valeur unique ou une liste de valeurs séparées par des virgules.
departementNoCode de département en deux ou trois chiffres. Ce paramètre filtre sur les établissements et accepte une valeur unique ou une liste de valeurs séparées par des virgules.
regionNoCode de région en deux chiffres. Ce paramètre filtre sur les établissements et accepte une valeur unique ou une liste de valeurs séparées par des virgules.
epciNoCode EPCI (établissement public de coopération intercommunale). Ce paramètre filtre sur les établissements et accepte une valeur unique ou une liste de valeurs séparées par des virgules.
est_associationNoUniquement les entreprises ayant un identifiant d'association ou une nature juridique avec mention 'association'.
est_entrepreneur_individuelNoUniquement les entreprises individuelles.
est_essNoUniquement les entreprises d'économie sociale et solidaire (ESS).
est_service_publicNoUniquement les structures reconnues comme administration (service public).
est_bioNoUniquement les entreprises ayant un établissement certifié par l'agence bio.
est_rgeNoUniquement les entreprises ayant au moins un établissement RGE (Reconnu Garant de l'Environnement).
est_finessNoUniquement les entreprises ayant au moins un établissement FINESS (établissements sanitaires et sociaux).
est_qualiopiNoUniquement les entreprises certifiées Qualiopi (organismes de formation).
est_societe_missionNoUniquement les sociétés à mission (article L.210-10 du code de commerce).
nom_personneNoNom d'un dirigeant ou élu (personne physique ou morale).
prenoms_personneNoPrénom(s) d'un dirigeant ou élu (personne physique).
type_personneNoType de personne recherchée : dirigeant ou élu.
ca_minNoChiffre d'affaires minimum (en euros).
ca_maxNoChiffre d'affaires maximum (en euros).
resultat_net_minNoRésultat net minimum (en euros).
resultat_net_maxNoRésultat net maximum (en euros).
pageNoNuméro de page des résultats (défaut : 1).
per_pageNoNombre de résultats par page (1 à 25, défaut : 10).
minimalNoRetourne une réponse minimale (sans tous les champs détaillés).
includeNoChamps à inclure avec minimal=true (complements, dirigeants, finances, matching_etablissements, siege, score).

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description must disclose behavioral traits. It only says 'searches many criteria' without mentioning pagination, rate limits, response format, or any side effects. This is insufficient for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and front-loaded. It conveys the core purpose without extraneous text. However, it could be slightly more informative while maintaining brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (32 parameters) and the absence of output schema, the description is too brief. It lacks details about return values, pagination, and API source. The sibling tool's presence also suggests a need for clearer context on when to use this one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with detailed descriptions for all 32 parameters. The description adds no new meaning beyond 'numerous criteria'. Baseline 3 is appropriate as the schema handles the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it searches French companies using multiple criteria like name, activity, location. It includes examples, but does not explicitly differentiate from the sibling tool 'rechercher_entreprise_geographiques', which likely focuses on geographic search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Given the sibling tool exists, explicit context or when-not-to-use instructions are missing. The description does not mention any prerequisites or scenario-specific advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

rechercher_entreprise_geographiquesB

Recherche des entreprises autour d'un point géographique (latitude, longitude, rayon, etc.).

ParametersJSON Schema
NameRequiredDescriptionDefault
latYesLatitude du point de recherche
longYesLongitude du point de recherche
radiusNoRayon de recherche en km (max 50km)
activite_principaleNoCode NAF ou code APE
section_activite_principaleNoSection de l'activité principale (A à U)
pageNoNuméro de page des résultats (défaut : 1).
per_pageNoNombre de résultats par page (1 à 25, défaut : 10).
minimalNoRetourne une réponse minimale (sans tous les champs détaillés).
includeNoChamps à inclure avec minimal=true (complements, dirigeants, finances, matching_etablissements, siege, score).

TDQS

B3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must convey behavioral traits. It only mentions basic parameters but lacks details on pagination, sorting, error handling, or result behavior (e.g., ordering by distance). The vague 'etc.' indicates incomplete disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but lacks structure. It uses 'etc.' which is vague and unprofessional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters, no output schema, and no annotations, the description is insufficient. It omits details on optional filters (activity types, pagination, minimal response) and does not explain the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds minimal extra meaning beyond mentioning lat, lon, radius, and 'etc.' Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches for companies around a geographic point, specifying key parameters (latitude, longitude, radius). It distinguishes from sibling tool 'rechercher_entreprise' which likely lacks geographic constraints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or context. It merely describes what the tool does without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

Les deux outils ont des finalités clairement distinctes : le premier permet une recherche générale par critères (nom, activité, localisation), le second se limite à une recherche géographique autour d'un point. Il n'y a pas de chevauchement.

Naming Consistency5/5

Les noms suivent un schéma cohérent : 'rechercher_entreprise' comme base, avec un qualificatif pour la variante géographique. La convention snake_case est uniforme et prédictible.

Tool Count3/5

Avec seulement 2 outils, le serveur est très ciblé. Pour un service de recherche d'entreprises, cela peut suffire si l'objectif est limité à la recherche, mais le nombre est à la limite inférieure de ce qui est raisonnable.

Completeness4/5

Les deux modes de recherche (général et géographique) couvrent les cas d'usage courants. Il manque peut-être une recherche par identifiant unique (SIRET) ou des opérations CRUD, mais dans le cadre d'un serveur dédié à la recherche, l'ensemble est presque complet.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP INPI

    ArnoLegi
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables querying French business registers (RNE, BODACC) and trademarks via INPI APIs. Provides tools to search companies, retrieve legal status, directors, beneficial owners, collective procedures, and trademark details.

  • France Business Intelligence

    fzthiait-ai
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to search and retrieve detailed profiles of 25 million French companies from the official government registry, including directors, activity codes, and establishment data, without requiring an API key.

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yoanbernabeu/mcp-recherche-entreprises'

If you have feedback or need assistance with the MCP directory API, please join our Discord server