siret-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIRENE_CACHE_TTL_MS | No | TTL for the cache in milliseconds. Defaults to 6 hours. | 21600000 |
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_companiesA | Find French companies by name, trade name, acronym or officer name. Fuzzy — 'boulangerie dupont nantes' works. Returns compact summaries; call get_company for the full profile. Filters are optional and combine with AND. |
| get_companyA | Full profile for one company from its SIREN (9 digits) or SIRET (14 digits). Returns legal form, activity, workforce bracket, headquarters, officers and certifications, all with plain-French labels. The |
| list_establishmentsA | All known sites (établissements) for a SIREN, headquarters first. Note: the registry returns matching establishments rather than an exhaustive list, so |
| explain_codeA | Translate a NAF activity code, catégorie juridique (legal form), workforce bracket, or administrative status into plain French. Offline — no API call. Use this instead of guessing what a code means. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| health | Cache statistics and version |
TDQS
Scored across 4 tools
Each tool has a clear, separate job: searching companies, retrieving a full company profile, listing establishment sites, and explaining registry codes. The cross-references between search_companies and get_company reinforce their complementary roles rather than creating ambiguity.
All tool names follow a consistent lowercase snake_case verb_noun pattern: search_companies, get_company, list_establishments, explain_code. The naming is uniform, predictable, and accurately reflects each action.
Four tools is well-scoped for a read-only French business registry lookup server. Each tool covers a distinct part of the workflow without unnecessary duplication or bloat.
The server covers the core lookup lifecycle: fuzzy search, full company profile retrieval, establishment enumeration, and code translation. Since this is a read-only registry service, CRUD operations are not expected, and there are no obvious dead ends in the workflow.