_ registry / mcp streamable-http · checked 6h ago

mana

https://mana.bzh

Registry code: b99422ca3e9642d0

api record

MANA connaît 3 764 277 lieux, commerces, professionnels et associations en France, rangés par code NAF de l'INSEE. Pour une question de terrain — « trouve-moi X près de Y » — appeler `commune` pour obtenir le code INSEE, puis `chercher`. Pour les associations, `associations` : c'est la seule source interrogeable du Répertoire National des Associations. Aucune donnée personnelle n'est rendue : la granularité géographique s'arrête à la commune.

endpoint
https://mana.bzh/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 mana live?
Yes — it answered the hub's last check (checked 6h ago). It answered 98% of checks over the last 30 days.
Is mana free to use?
Not measured yet.
What tools does mana have?
5 tools: commune, missions, chercher, catalogue, associations.
Is mana 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
98.1%

90 days 98.7%· all time 98.7%

latency
128ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 377 checks · signed record
  • down → live
  • degraded → down· HTTP 503
  • live → degraded· HTTP 503
  • down → live
  • degraded → live
_ what it is for
used for
  • find businesses and places in france near a town
  • look up a commune insee code
  • list associations in a commune
  • find volunteering missions
takes → gives
text → data
tools
5 reads
_ 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

_ what it can do 5 tools
5 never probed 0 of 5 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.

  • commune reads unknown never probed

    Trouve le code INSEE d'une commune à partir de son nom. À appeler EN PREMIER : `chercher`, `associations` et `missions` attendent un code INSEE, jamais un nom. Attention, un code INSEE n'est pas un code postal (Crozon : 29042 et 29160).

    mcp-tool

    {
      "type": "object",
      "required": [
        "nom"
      ],
      "properties": {
        "nom": {
          "type": "string",
          "description": "Nom de la commune"
        }
      }
    }
    arguments 12 lines
  • missions reads unknown never probed

    Les missions de bénévolat ouvertes, relayées du réseau public API Engagement. Chaque mission porte l'URL de sa source : la candidature se fait chez l'organisateur, jamais ici.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limite": {
          "type": "integer"
        },
        "commune": {
          "type": "string",
          "description": "Code INSEE"
        },
        "departement": {
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • chercher reads unknown never probed

    Cherche un lieu, un commerce, un artisan, un professionnel de santé, une association ou un événement en France. À appeler pour toute question du type « trouve-moi X près de Y ». Interroge 3 764 277 fiches actives, rangées par CODE NAF de l'INSEE — pas par mots-clés. Accepte aussi un numéro SIRET (14 chiffres) ou SIREN (9). NE REND NI ADRESSE NI TÉLÉPHONE : la granularité s'arrête à la commune.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Texte libre, ou un numéro SIRET / SIREN"
        },
        "limite": {
          "type": "integer",
          "description": "De 1 à 50 (défaut 20)"
        },
        "commune": {
          "type": "string",
          "description": "Code INSEE (5 caractères). Appeler `commune` pour l'obtenir depuis un nom."
        },
        "categorie": {
          "enum": [
            "repas",
            "soin",
            "beaute",
            "artisan",
            "habitat",
            "boutique",
            "transport",
            "sortie",
            "hotel",
            "demarche",
            "entraide"
          ],
          "type": "string",
          "description": "Une des 11 catégories. Ne se combine pas avec « q » : le rangement l'emporte sur le texte."
        },
        "departement": {
          "type": "string",
          "description": "Code de département, ex. « 29 »"
        },
        "sous_categorie": {
          "type": "string",
          "description": "Ex. « boulange », « kiné », « plombier ». Appeler `catalogue` pour la liste."
        }
      }
    }
    arguments 42 lines
  • catalogue reads unknown never probed

    Rend les 11 catégories et leurs sous-catégories, avec le nombre de fiches de chacune. À appeler AVANT `chercher` quand on ne sait pas quel terme employer : les sous-catégories sont un vocabulaire fermé, deviner un nom rend une liste vide.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • associations reads unknown never probed

    Les associations déclarées d'une commune ou d'un département, avec leur objet social, issues du Répertoire National des Associations. Utile pour « quelle association fait X près de Y » — une question à laquelle aucune autre source ne répond. NE REND PAS DE CONTACT : le RNA n'en publie aucun, délibérément.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Un mot du nom de l'association"
        },
        "limite": {
          "type": "integer"
        },
        "commune": {
          "type": "string",
          "description": "Code INSEE"
        },
        "departement": {
          "type": "string",
          "description": "Code de département"
        }
      }
    }
    arguments 20 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 b99422ca3e9642d0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b99422ca3e9642d0/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/b99422ca3e9642d0/badge.svg)](https://brick.blue/agent/b99422ca3e9642d0?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
90%

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.