mcp-recherche-entreprise
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_TIMEOUT | No | Timeout pour les requêtes API en millisecondes | |
| API_RATE_LIMIT | No | Limite de taux pour les requêtes API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_companiesB | Rechercher des entreprises via l'API recherche-entreprises.api.gouv.fr |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap in functionality. The purpose of 'search_companies' is unambiguous.
The sole tool name follows a clear verb_noun pattern ('search_companies'), which is consistent and predictable. Even with one tool, the naming style is sound.
A single tool feels thin for a server, but the purpose ('recherche-entreprise') is narrowly scoped to company search. It is borderline acceptable, though additional tools would round out the offering.
The tool covers the core search operation, but lacks related functionality such as retrieving a company by SIREN or fetching detailed records. Agents can perform basic lookups but hit dead ends for more specific queries.