arcep-eligibility-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCEP_API_KEY | Yes | Your ARCEP API key |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fixed_line_eligibilitiesA | Get fixed-line eligibilities for an address from the ARCEP API. Chains town lookup, address lookup, building lookup, and eligibility fetch. |
| get_mobile_eligibilitiesB | Get mobile eligibilities for an address from the ARCEP API. |
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 2 tools
The two tools are clearly separated by service type: fixed-line versus mobile eligibility. There is no overlap or ambiguity in their purposes.
Both tools follow the exact same get_<type>_eligibilities pattern, using consistent snake_case and a clear verb-noun structure.
With only two tools, the server feels minimal, but the count aligns with its narrow ARCEP eligibility scope. It is on the thin side but not unreasonably so.
The server covers both major eligibility domains (fixed-line and mobile) for the ARCEP API. A minor gap is the lack of separate address lookup or offer detail tools, but the core eligibility workflows are implemented.