Skip to main content
Glama
Sign In
arcep-eligibility-mcp-server

arcep-eligibility-mcp-server

by laurentluce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ARCEP Eligibility MCP Server

An MCP server that queries the ARCEP eligibility API to check fixed-line and mobile telecom eligibilities for a given address in France.

Tools

get_fixed_line_eligibilities

Returns fixed-line eligibility data for a given street address and town in France.

Parameters:

Name

Type

Description

streetAddress

string

Street address (e.g. "10 rue de la Paix")

townName

string

Town name (e.g. "Paris")

get_mobile_eligibilities

Returns mobile eligibility data for a given street address and town in France.

Parameters:

Name

Type

Description

streetAddress

string

Street address (e.g. "10 rue de la Paix")

townName

string

Town name (e.g. "Paris")

Related MCP server: risques_territoire_mcp

Setup

Prerequisites

  • Node.js 18+

  • An ARCEP API key

Build

npm install
npm run build

Configuration

Set the ARCEP_API_KEY environment variable:

export ARCEP_API_KEY=your_api_key

Usage with Claude Desktop

Add to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "arcep-eligibility": {
      "command": "node",
      "args": ["/absolute/path/to/arcep-api-eligibility-mcp-server/build/index.js"],
      "env": {
        "ARCEP_API_KEY": "your_api_key"
      }
    }
  }
}

License

ISC

Available Tools

2 tools
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.

Inputs: townName (required), streetAddress (required).

get_mobile_eligibilitiesB

Get mobile eligibilities for an address from the ARCEP API.

Inputs: townName (required), streetAddress (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly separated by service type: fixed-line versus mobile eligibility. There is no overlap or ambiguity in their purposes.

    Naming Consistency5/5

    Both tools follow the exact same get_<type>_eligibilities pattern, using consistent snake_case and a clear verb-noun structure.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers