_ registry / mcp streamable-http · checked 58m ago

france-care

https://mcp.france-care.fr

Registry code: c1da8bd61279982e

api record

Données publiques agrégées de l'offre de soins en France (DREES, FINESS, RNA, INSEE). Orienter, jamais diagnostiquer. Méthodologie et couverture : ressources france-care://methodology et france-care://coverage.

endpoint
https://mcp.france-care.fr/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is france-care live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is france-care free to use?
Yes — the hub reached it with no key and no payment.
What tools does france-care have?
4 tools: compare_territories, signaler_besoin_non_couvert, search_health_infrastructure, analyze_territory.
Is france-care safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
94ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • compare_territories unknown 58m ago

    Compare l'acces aux soins entre 2 territoires francais. Chaque territoire peut etre un code postal, un nom de commune, ou un code INSEE prefixe (insee:77186). Exactement 2 territoires par appel.

    mcp-tool

    {
      "type": "object",
      "required": [
        "territories"
      ],
      "properties": {
        "territories": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 2,
          "minItems": 2,
          "description": "Exactement 2 territoires (codes postaux, noms, ou codes INSEE prefixes insee:)"
        }
      }
    }
    arguments 17 lines
  • signaler_besoin_non_couvert unknown never probed

    Enregistre, sans aucune donnee personnelle, qu'une personne n'a pas trouve de soignant pour un besoin donne dans sa commune. A utiliser quand la personne demande a signaler ce manque ou l'accepte. Commune, profession et nature du manque sur listes fermees ; aucun texte libre, aucune identite. France Care agrege ces signalements par territoire.

    mcp-tool

    {
      "type": "object",
      "required": [
        "commune",
        "profession",
        "manque"
      ],
      "properties": {
        "manque": {
          "enum": [
            "aucun_praticien_proche",
            "pas_de_nouveaux_patients",
            "delai_trop_long",
            "trop_loin",
            "autre"
          ],
          "type": "string",
          "description": "Nature du manque constate"
        },
        "commune": {
          "type": "string",
          "description": "Code postal, code INSEE prefixe (insee:77186) ou nom exact de la commune"
        },
        "profession": {
          "enum": [
            "medecin_generaliste",
            "dentiste",
            "kinesitherapeute",
            "infirmier",
            "sage_femme",
            "pediatre",
            "gynecologue",
            "ophtalmologue",
            "psychiatre",
            "dermatologue",
            "cardiologue",
            "autre_specialiste"
          ],
          "type": "string",
          "description": "Profession recherchee"
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • search_health_infrastructure unknown 58m ago

    Recherche des etablissements de sante dans la base FINESS. Permet de lister les EHPAD, hopitaux, pharmacies, maisons de sante, laboratoires, cliniques, SSIAD, centres de dialyse, etc. Deux modes: (1) Par limites administratives: commune, code postal, code INSEE prefixe (insee:77186), departement. (2) Par proximite: avec radius_km, recherche dans un rayon autour du lieu, resultats tries par distance. Utilise radius_km quand l'utilisateur demande les etablissements "les plus proches", "a proximite", ou "dans un rayon de X km".

    mcp-tool

    {
      "type": "object",
      "required": [
        "location"
      ],
      "properties": {
        "type": {
          "type": "string",
          "description": "Type d'etablissement recherche. Exemples: ehpad, hopital, pharmacie, clinique, laboratoire, maison de sante, centre de sante, ssiad, dialyse, psychiatrie, had, maison de retraite. Optionnel — si absent, retourne tous les types."
        },
        "limit": {
          "type": "number",
          "description": "Nombre max de resultats (defaut: 50, max: 100)"
        },
        "location": {
          "type": "string",
          "description": "Lieu de recherche: code postal (77300), code departement (77), ou nom de commune (Fontainebleau)"
        },
        "radius_km": {
          "type": "number",
          "description": "Rayon de recherche en km (1-50). Active la recherche par proximite avec tri par distance. Si absent, recherche par limites administratives (commune/departement)."
        }
      }
    }
    arguments 24 lines
  • analyze_territory unknown 58m ago

    Analyse l'acces aux soins d'un territoire francais. Accepte un code postal (ex: 77300), un nom de commune (ex: Fontainebleau), ou un code INSEE prefixe (ex: insee:77186) ; sans prefixe, 5 chiffres se lisent d'abord comme un code postal. Si plusieurs communes correspondent, la reponse les liste avec la requete exacte a relancer (relancer_avec). Retourne: APL medecins generalistes et niveau d'acces rapporte a la moyenne nationale, infrastructure sante (FINESS), associations sante (RNA), organisation des soins (CPTS, TDS), population active, et comparaison regionale/nationale. Retourne aussi les classements officiels de la commune (seuil DREES de commune sous-dense, zonage de l'ARS pour six professions avec date d'arrete, zone prioritaire du Pacte de lutte contre les deserts medicaux). Sources: DREES (APL, millesime 2023), FINESS (synchronise chaque jour), RNA, ARS, ministere de la Sante.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Code postal, nom de commune, ou code INSEE prefixe (insee:77186)"
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c1da8bd61279982e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c1da8bd61279982e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c1da8bd61279982e/badge.svg)](https://brick.blue/agent/c1da8bd61279982e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on france-care.fr 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.