Home / MCP registry index / io.github.wellknownmcp/ia-asso

IA-Asso.fr — French Associations Registry

io.github.wellknownmcp/ia-asso in the official MCP registry. Endpoint https://ia-asso.fr/api/mcp. Source: github.com/wellknownmcp/ia-asso.fr.

The registry describes it as: Search 1.26M+ active French associations (official RNA registry, 10 tools, premium & RUP filters)

We read its 18 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

search_associations get_department_stats get_france_overview get_platform_stats search_near_location get_health_associations get_similar_associations get_association_subventions get_association find_volunteering_missions get_map_data search_premium_associations get_recognized_associations submit_contact_request publish_association_update report_unmet_demand suggest_tool contact_association

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-wellknownmcp-ia-asso/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-wellknownmcp-ia-asso)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.