france-mcp
Related Servers
Alternatives to france-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with access to French public registries including company records, property sale prices, housing energy performance, and short-term rental rates via MCP tools.-
- AlicenseAqualityCmaintenanceEnables AI assistants to query French public open data through read-only tools: geocoding and reverse geocoding of addresses, company lookups by name, address, leader or SIREN, and commune listings by name, postcode or département. It wraps free, keyless government APIs (IGN Géoplateforme/BAN, Recherche d'entreprises/SIRENE, geo.api.gouv.fr) over stdio or Streamable HTTP with validated inputs and rate limiting.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query official French data — company records (SIREN), BODACC legal notices, address geocoding and Géorisques hazard reports — through MCP tools paid per call in USDC on Base via x402, with no account or API key required. Built-in spending guardrails and a wallet-free discovery mode keep payments bounded and safe.MIT
- AlicenseAqualityAmaintenanceFrance Data MCP lets AI agents query, cross-reference and automatically enrich multiple French public registries through a unified MCP interface. France Data MCP provides a French territorial intelligence layer designed for multi-source reasoning and agentic orchestration.37245 npm4MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityCmaintenanceFrench company data for AI agents: directors with probable business email, people search, counterparty checks (KYB) and hiring signals from official registries. Paid per call with x402 (USDC on Base or Solana), charged only when found.98 npmMIT
TDQS
Scored across 19 tools
Most tools target clearly distinct resources and actions: detail-vs-search pairs (entreprises_fiche/entreprises_rechercher, marches_avis/marches_rechercher, datagouv_*), forward vs reverse geocoding, and DVF listings vs statistics are all separable. Minor overlap exists between communes_rechercher and territoire_lister (both can enumerate communes) and the marches_avis/marches_rechercher naming only hints at detail-vs-search, but descriptions resolve it.
A clear resource_action convention dominates (entreprises_rechercher, communes_rechercher, dpe_rechercher, services_publics_trouver, territoire_lister), with a few noun-only names (dvf_ventes, risques_adresse, jours_feries, energie_postes_sources). All snake_case and domain-prefixed, so it stays predictable despite the small deviation.
19 tools is on the heavy side, but this is a multi-domain French open-data hub where each tool maps to a distinct upstream source (Sirene, BAN, BOAMP, DVF, Géorisques, ADEME, data.gouv, Caparéseau, Service-Public). No obvious filler or redundant tool earns a slot without purpose.
The surface covers the major French public-data workflows end to end: geocode → commune → cadastre → DVF/DPE/risks, plus business lookup, procurement, datasets, grid capacity, public services and holidays. Gaps are minor and domain-adjacent (e.g. no routing/transport, no direct file download or write operations), not blockers for the stated purpose.