Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MANA — la vie locale française

REMOTE · MANA.BZH

Lieux, commerces, artisans et associations en France — 3,7 M de fiches, rangées par code NAF.

Available components

0 this week 79 Trust /100

Last scanned (17 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 711 tokens (~142/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +54
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 3 Nov 26 −54
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 30 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mana.bzh/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mana.bzh CN=YE2,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA384 653956083ecc80135816ef3b344a0d250c2
SANs: mana.bzh
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mana.bzh. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
bzh. DS published 54187 13 Verified
mana.bzh. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mana.bzh/mcp Verified 200
http (plaintext) http://mana.bzh/mcp HTTPS enforced 308 https://mana.bzh/mcp
MCP tools · 5 exposed · ~600 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
associations ~117

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.

NameTypeReqDescription
communestring–Code INSEE
departementstring–Code de département
limiteinteger––
qstring–Un mot du nom de l'association

No output schema declared.

No examples provided.

catalogue ~64

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chercher ~265

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.

NameTypeReqDescription
categoriestring–Une des 11 catégories. Ne se combine pas avec « q » : le rangement l'emporte sur le texte.
communestring–Code INSEE (5 caractères). Appeler `commune` pour l'obtenir depuis un nom.
departementstring–Code de département, ex. « 29 »
limiteinteger–De 1 à 50 (défaut 20)
qstring–Texte libre, ou un numéro SIRET / SIREN
sous_categoriestring–Ex. « boulange », « kiné », « plombier ». Appeler `catalogue` pour la liste.

No output schema declared.

No examples provided.

commune ~85

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).

NameTypeReqDescription
nomstringyesNom de la commune

No output schema declared.

No examples provided.

missions ~69

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.

NameTypeReqDescription
communestring–Code INSEE
departementstring––
limiteinteger––

No output schema declared.

No examples provided.

Install

How do I install the MANA — la vie locale française MCP server?

MANA — la vie locale française is a hosted endpoint at https://mana.bzh/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mana.bzh

# add to Claude Code
claude mcp add --transport http bzh-mana-mana 'https://mana.bzh/mcp'
Common questions

What is the MANA — la vie locale française MCP server?

MANA — la vie locale française is an MCP server listed in the public MCP registry as bzh.mana/mana. Lieux, commerces, artisans et associations en France, 3,7 M de fiches, rangées par code NAF. This page covers its hosted endpoint (https://mana.bzh/mcp).

Is the MANA — la vie locale française MCP server safe to use?

MANA — la vie locale française scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MANA — la vie locale française MCP server expose?

MANA — la vie locale française exposes 5 tools: chercher, catalogue, commune, associations, missions. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.

Does the MANA — la vie locale française MCP server require authentication?

No. We connected to MANA — la vie locale française without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MANA — la vie locale française MCP server still maintained?

MANA — la vie locale française is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MANA — la vie locale française MCP server?

VerifyMCP ran 12 checks on MANA — la vie locale française, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MANA — la vie locale française: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.