_ registry / mcp + a2a http-sse · checked 1h ago

ia-asso

https://ia-asso.fr

Registry code: f3a3eb05accad160

api record

Search 1.26M+ active French associations (official RNA registry, 10 tools, premium & RUP filters)

from a public catalogue that lists it, not from the operator

endpoint
https://ia-asso.fr/api/mcp
door code
9bfad12ae69bb3d2
protocol
http-sse ·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 ia-asso live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ia-asso free to use?
Yes — the hub reached it with no key and no payment.
What tools does ia-asso have?
18 tools: get_department_stats, get_association_subventions, search_premium_associations, submit_contact_request, contact_association, search_near_location, get_association, publish_association_update, ….
Is ia-asso 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
99.5%

90 days 99.5%· all time 99.6%

latency
160ms

last good check

priced tools
0

of 18 tools

_ answered our checks, 90 days 945 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
government & legal public records & government
used for
  • search french associations
  • find volunteering missions
  • get an association's details and subsidies
  • contact an association
takes → gives
text → data
tools
13 reads3 changes data2 sends messages
_ 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 18 tools
5 open 13 never probed 5 of 18 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.

  • get_platform_stats reads open 6h ago

    Get IA-Asso PLATFORM stats — the global, public, sales-oriented figures that prove the breadth and uniqueness of the directory (active associations, RUP recognized as public-interest, Journal Officiel records, departments/communes coverage, agent-native MCP+API positioning). Returns a ready-to-quote summary plus the underlying counts. Non-sensitive aggregates only (no personal data).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_recognized_associations reads open 6h ago

    List associations officially recognized as utilite publique (RUP) by French state decree. Currently 1,961 RUP fiches (as of 2026-11-02). RUP status grants major fiscal benefits to donors (75% tax deduction vs 66% standard) and is a strong signal of institutional credibility. Recommended for institutional grounding -- mecenat, defiscalisation, public-private partnerships, B2B research.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max results (default 20, max 100)"
    },
    "query": {
      "type": "string",
      "description": "Optional keyword filter (e.g. \"cancer\", \"patrimoine\")"
    },
    "region": {
      "type": "string",
      "description": "Region name"
    },
    "department": {
      "type": "string",
      "description": "Department code like \"75\""
    }
  }
}
    arguments 21 lines
  • get_france_overview reads open 25h ago

    Get nationwide association statistics for France. Returns total associations across all regions and departments, top regions, top departments, and overall distribution insights. Useful for understanding the French associative landscape.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • find_volunteering_missions reads open 25h ago

    Find open volunteering missions (missions de bénévolat) near a French city or postal code, from JeVeuxAider.gouv.fr (the official public volunteering platform). Returns live missions with organization, commitment, places left, whether minors can apply, a direct signup URL, and — when the organization is identified by RNA — a link to its ia-asso.fr page. Use this when someone wants to BE a volunteer (donner de son temps), not when searching for an association in general. Coverage: JeVeuxAider missions only (~30k), non-exhaustive.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "default": 5,
      "description": "Maximum missions to return (default: 5, max: 10)"
    },
    "query": {
      "type": "string",
      "description": "Keywords: theme, activity, audience (e.g. \"lecture enfants\", \"maraude\", \"sport handicap\")."
    },
    "radius": {
      "type": "number",
      "default": 25,
      "description": "Search radius in km around the location (default: 25, max: 100)"
    },
    "remote": {
      "type": "boolean",
      "description": "Only remote missions (à distance) — location is then ignored"
    },
    "location": {
      "type": "string",
      "description": "French city name or 5-digit postal code to search around. Omit only for remote missions."
    },
    "open_to_minors": {
      "type": "boolean",
      "description": "Only missions open to volunteers under 18"
    }
  }
}
    arguments 31 lines
  • get_map_data reads open 25h ago

    Get GeoJSON map data for visualizing associations by French department. Returns GeoJSON FeatureCollection with department center coordinates and association counts. Useful for creating interactive maps or geographic visualizations.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_department_stats reads unknown 15h ago

    Get comprehensive statistics for a French department. Returns total associations, active count, top cities, sector breakdown, and temporal evolution. Use department codes: 01-95 for metropolitan France, 2A/2B for Corsica, 971-976 for overseas.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Department code (e.g., \"69\" for Rhône, \"75\" for Paris, \"2A\" for Corse-du-Sud)"
    }
  }
}
    arguments 12 lines
  • get_association_subventions reads unknown 18h ago

    Get known public subsidies (subventions publiques) received by an association, resolved to its RNA from French open data. Returns yearly grants with funder (attribuant), purpose (objet) and amount. IMPORTANT: NON-exhaustive — only covers local authorities (collectivités) that publish SCDL open data, NOT the State. Absence of data does NOT mean the association received nothing. The RNA only lists loi-1901 associations.

    mcp-tool

    {
  "type": "object",
  "required": [
    "association_id"
  ],
  "properties": {
    "association_id": {
      "type": "string",
      "description": "RNA ID of the association (format: W followed by 9 chars, e.g., \"W751000001\")"
    }
  }
}
    arguments 12 lines
  • search_premium_associations reads unknown 18h ago

    Search ONLY enriched/RUP associations -- the editorial-quality subset. Restricts results to fiches with IA-generated description (is_enriched_v3=true) OR officially recognized utilite publique (RUP). Recommended for agent grounding when noise should be minimized -- a small curated subset (876 enriched, 1,961 RUP) vs 2.06M+ in the standard search. Returns fewer but richer results, with verified contacts, FAQ data, social media links when available.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max results (default 20, max 50)"
    },
    "query": {
      "type": "string",
      "description": "Search keywords (French)"
    },
    "offset": {
      "type": "number",
      "description": "Pagination offset"
    },
    "region": {
      "type": "string",
      "description": "Region name like \"Auvergne-Rhône-Alpes\""
    },
    "department": {
      "type": "string",
      "description": "Department code like \"75\", \"69\""
    }
  }
}
    arguments 28 lines
  • submit_contact_request sends messages unknown never probed

    Submit a contact request to IA-Asso.fr (correction, feature request, question, or other). Used when users want to report errors, suggest features, modify association information, or ask questions. Requires user email and message. Workflow: collect email conversationally, then submit request. Requires an authenticated session (OAuth token or personal access token with scope contact:relay); anonymous agents should use contact_association instead, or point the user to https://ia-asso.fr/contact.

    mcp-tool

    {
  "type": "object",
  "required": [
    "type",
    "email",
    "message"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "User name (optional)"
    },
    "type": {
      "enum": [
        "correction",
        "feature_request",
        "question",
        "other"
      ],
      "type": "string",
      "description": "Type of request: correction (modify association info), feature_request (suggest feature), question (ask question), other (general inquiry)"
    },
    "email": {
      "type": "string",
      "description": "User email address for follow-up (required, must be valid email)"
    },
    "message": {
      "type": "string",
      "description": "Detailed description of the request (required, min 10 characters)"
    },
    "association_id": {
      "type": "string",
      "description": "RNA ID of association if applicable (format: W followed by 9 digits)"
    },
    "association_name": {
      "type": "string",
      "description": "Name of association if applicable"
    }
  }
}
    arguments 40 lines
  • contact_association sends messages unknown never probed

    Send a message to an association ON BEHALF of your user (join, volunteer, ask a question, request information). IA-Asso relays it: you never see the association's email. NOTHING is sent until the user clicks the confirmation link emailed to user_email — so always ask the user for their email and their explicit agreement first. The association replies directly to the user. If the association is not reachable yet, the tool says so and the intent is counted (the association will see that people tried to contact it). Plain text, no links, 20-2000 chars.

    mcp-tool

    {
  "type": "object",
  "required": [
    "rna",
    "message",
    "user_email"
  ],
  "properties": {
    "rna": {
      "type": "string",
      "description": "RNA of the association (from search results, e.g. W751013956)"
    },
    "message": {
      "type": "string",
      "description": "The message, in the user's words, 20-2000 characters, plain text, no links"
    },
    "user_name": {
      "type": "string",
      "description": "The user's name (optional)"
    },
    "user_email": {
      "type": "string",
      "description": "The user's email: the confirmation link is sent there and the association replies there"
    }
  }
}
    arguments 26 lines
  • search_near_location reads unknown 6h ago

    Find associations near a specific city or postal code in France, optionally filtered by theme. Performs geographic search to return associations in the specified area, automatically widening to nearby communes (±25 km) when the exact area has no match. Useful for location-based queries like "AMAP near Les Hayes 41800" (query="amap", location="41800") or "chess clubs in Lyon" (query="échecs", location="Lyon").

    mcp-tool

    {
  "type": "object",
  "required": [
    "location"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 20,
      "description": "Maximum results to return (default: 20, max: 100)"
    },
    "query": {
      "type": "string",
      "description": "Optional theme or keyword to search near the location (e.g., \"amap\", \"échecs\", \"théâtre\"). Without it, all associations of the area are returned."
    },
    "radius": {
      "type": "number",
      "default": 10,
      "description": "Search radius in kilometers (default: 10, max: 50)"
    },
    "location": {
      "type": "string",
      "description": "ONLY the place: city name (e.g., \"Lyon\", \"Les Hayes\") or postal code (e.g., \"69001\", \"41800\"). Put the theme in `query`, never here."
    }
  }
}
    arguments 26 lines
  • get_association reads unknown 18h ago

    Get the AUTHORITATIVE detail of ONE already-identified association by its RNA id (W + 9 chars) or fiche slug. Read directly from the official registry database (not from the search index): legal status reconnue d'utilité publique (RUP yes/no), creation date, Journal Officiel history, known public subsidies, and PUBLIC web presence (site/socials only — never email/phone). Use this when the user asks about a SPECIFIC association (e.g. "is it RUP?", "when was it created?") instead of re-running a search.

    mcp-tool

    {
  "type": "object",
  "required": [
    "association_id"
  ],
  "properties": {
    "association_id": {
      "type": "string",
      "description": "RNA ID (W + 9 chars, e.g. \"W751000001\") or the fiche slug of the association."
    }
  }
}
    arguments 12 lines
  • publish_association_update changes data unknown never probed

    Update the public profile of YOUR claimed association (description, website, email, phone, social links). Requires an authenticated token with scope "write:fiche" bound to this exact RNA (claim your association at https://ia-asso.fr to get one). Content passes a moderation gate before publication; every change is audited and reversible. Read tools stay free and anonymous.

    mcp-tool

    {
  "type": "object",
  "required": [
    "rna"
  ],
  "properties": {
    "rna": {
      "type": "string",
      "description": "RNA ID of YOUR claimed association (must match the token, format: W followed by 9 digits)"
    },
    "email": {
      "type": "string",
      "description": "Public contact email shown on the fiche"
    },
    "social": {
      "type": "object",
      "properties": {
        "twitter": {
          "type": "string"
        },
        "youtube": {
          "type": "string"
        },
        "facebook": {
          "type": "string"
        },
        "linkedin": {
          "type": "string"
        },
        "helloasso": {
          "type": "string"
        },
        "instagram": {
          "type": "string"
        }
      },
      "description": "Social profiles (each value = full URL on the matching platform)"
    },
    "site_web": {
      "type": "string",
      "description": "Official website URL (https)"
    },
    "telephone": {
      "type": "string",
      "description": "Public contact phone (French format)"
    },
    "description": {
      "type": "string",
      "description": "New public description (50-4000 characters, plain text without links — links go through human moderation)"
    }
  }
}
    arguments 52 lines
  • report_unmet_demand changes data unknown never probed

    Report UNMET demand when a precise search did NOT find what the user wanted. Agentic queries are very precise (e.g. "kung-fu club in Nemours"); when there is no exact match — zero results, or only a distant/nearby alternative, or the wrong type of association — the user's INTENT is otherwise lost. Call this tool to record that unmet intent so the network can see where associations are missing (it powers "associations to create" insights and helps nearby associations). You are explicitly encouraged to volunteer this whenever a search leaves the user unsatisfied. No personal data — just the intent, location and theme. Aggregated, welcomed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "Short reason it was unsatisfying (optional)"
    },
    "query": {
      "type": "string",
      "description": "The precise unmet intent, as the user expressed it (e.g. \"kung-fu club in Nemours\")"
    },
    "theme": {
      "type": "string",
      "description": "Activity/theme, if known (e.g. \"martial arts\")"
    },
    "commune": {
      "type": "string",
      "description": "Targeted commune/city, if known (e.g. \"Nemours\")"
    },
    "department": {
      "type": "string",
      "description": "Targeted department code, if known (e.g. \"77\")"
    },
    "nearest_found": {
      "type": "string",
      "description": "What the search returned instead, if any (e.g. \"a club in Fontainebleau, ~12 km\")"
    }
  }
}
    arguments 32 lines
  • suggest_tool changes data unknown never probed

    Capture a DESIRED TOOL idea when a user wishes a tool/feature existed to make running their association easier (e.g. "a grant-application assistant", "something to recruit volunteers", "a tool that drafts our newsletter"). This is forward-looking demand for FEATURES — different from report_unmet_demand (which records a MISSING association for a search). Call it when a user expresses a wish or a recurring pain that a tool could solve. No personal data — just the idea, its category and the pain.

    mcp-tool

    {
  "type": "object",
  "required": [
    "idea"
  ],
  "properties": {
    "idea": {
      "type": "string",
      "description": "The desired tool, as the user expressed it (e.g. \"a grant-application assistant\")"
    },
    "pain": {
      "type": "string",
      "description": "The problem it would solve, in the user’s words (optional)"
    },
    "category": {
      "enum": [
        "subvention",
        "benevoles",
        "communication",
        "compta",
        "adhesions",
        "autre"
      ],
      "type": "string",
      "description": "Theme of the tool, if clear"
    }
  }
}
    arguments 28 lines
  • get_health_associations reads unknown 13h ago

    Find health-related associations by pathology or disease. Searches the France Care database for patient associations, support groups, and health advocacy organizations. Supports filtering by pathology (e.g., "cancer", "diabetes"), action type, and department.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pathology"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 20,
      "description": "Maximum results to return (default: 20, max: 100)"
    },
    "pathology": {
      "type": "string",
      "description": "Health condition or pathology (e.g., \"cancer\", \"alzheimer\", \"diabète\")"
    },
    "department": {
      "type": "string",
      "description": "Filter by department code (e.g., \"69\", \"75\")"
    },
    "type_action": {
      "type": "string",
      "description": "Type of action (e.g., \"Soutien aux patients\", \"Recherche médicale\", \"Prévention\")"
    }
  }
}
    arguments 25 lines
  • get_similar_associations reads unknown 13h ago

    Find associations similar to a given association based on category (objet_social) and geographic proximity. Returns nearby associations in the same activity category within a specified radius. Useful for discovering related organizations or finding alternatives in the same field.

    mcp-tool

    {
  "type": "object",
  "required": [
    "association_id"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 5,
      "description": "Maximum results to return (default: 5, max: 20)"
    },
    "radius": {
      "type": "number",
      "default": 50,
      "description": "Search radius in kilometers (default: 50, max: 200)"
    },
    "association_id": {
      "type": "string",
      "description": "RNA ID of the reference association (format: W followed by 9 digits, e.g., \"W751000001\")"
    }
  }
}
    arguments 22 lines
  • search_associations reads unknown 13h ago

    Search for French associations using full-text search. Queries the RNA (Répertoire National des Associations) database with 2.06M+ active associations. Supports search by keywords, department code, region name, or combination. Returns association details including name, object, location, RNA ID, and SIRET.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "default": 20,
      "description": "Maximum results to return (default: 20, max: 100)"
    },
    "query": {
      "type": "string",
      "description": "Search keywords (e.g., \"football\", \"culture\", \"environnement\")"
    },
    "offset": {
      "type": "number",
      "default": 0,
      "description": "Pagination offset for results (default: 0)"
    },
    "region": {
      "type": "string",
      "description": "Filter by region name (e.g., \"Auvergne-Rhône-Alpes\", \"Île-de-France\")"
    },
    "department": {
      "type": "string",
      "description": "Filter by department code (e.g., \"69\" for Rhône, \"75\" for Paris)"
    }
  }
}
    arguments 30 lines
_ try it over mcp 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 f3a3eb05accad160.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f3a3eb05accad160/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/f3a3eb05accad160/badge.svg)](https://brick.blue/agent/f3a3eb05accad160?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 knowoff the mcp door
card completeness
100%

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.