Skip to main content
Glama
Hug0x0

mcp-local-risk-france

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-local-risk-france

No user-submitted related servers found.

    Related Servers

    • mcp-gouv-fr

      gghez
      A
      license
      A
      quality
      D
      maintenance
      MCP server for exploring French public open data via APIs like data.gouv.fr, geo.api.gouv.fr, INSEE Sirene, and Radio France.
      11
      MIT

    • mcp-mayotte

      Hug0x0
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Mayotte public data, vigilance, administrative references, and local risk discovery, enabling users to search datasets, list communes, and fetch official information.
      10
      MIT

    • mcp-service-public

      OneNicolas
      A
      license
      Not graded
      quality
      F
      maintenance
      This MCP server provides access to over 38 French public data sources. It enables queries on legal, fiscal, real estate, educational, and other administrative information.
      6
      MIT

    • nyambot-mcp

      GabMJ23
      A
      license
      A
      quality
      C
      maintenance
      A French administration MCP server that enables AI agents to access official public data including communes, geocoding, property risks, and energy performance certificates (DPE) for real estate evaluation.
      4
      MIT

    • mcp-datagouv-fr

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the French open-data catalogue data.gouv.fr, enabling dataset search and retrieval, organization lookup, and reuse discovery via natural language queries.
      1 npm
      MIT

    • geocontext

      mborne
      A
      license
      Not graded
      quality
      F
      maintenance
      An experimental MCP server providing spatial context for LLMs by interfacing with French Geoplateforme services. It enables tasks such as geocoding, altitude lookups, and querying administrative, cadastral, or urban planning data.
      7 npm
      4
      MIT
    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.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools are mostly distinct: one for sources, two for data.gouv search/inspect, one for fetching excerpts, one for scope explanation, one for reference items, and several for commune-specific risk lookups (find, links, radon, seismic, brief). Slight overlap between search_data_gouv and search_risk_datasets — the latter adds topic+context but they could be confused.

    Naming Consistency4/5

    All tools share the 'local_risk_france_' prefix, which creates a strong brand and pattern, and most verbs are clear (get, search, find, fetch, list, explain). Minor inconsistency: 'get_georisques_links' vs 'get_seismic_zoning' vs 'get_radon' — the last two target specific data types while the first returns links, but verbs are uniform enough.

    Tool Count5/5

    12 tools is well within the sweet spot for a domain-specific MCP. Each tool covers a distinct need: navigation, data retrieval, lookup, and briefing. None feel redundant; a few are meta (explain_scope, list_reference_items) but useful for agent onboarding.

    Completeness4/5

    The surface covers essential workflows: discover sources, search datasets, inspect datasets, resolve communes, fetch official links and specific data (radon, seismic), and generate a brief. Minor gaps: no direct tool to fetch data from a data.gouv dataset (only inspect metadata) and no tool to fetch full source content beyond a short excerpt, but agents can combine tools to achieve this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources