Home / MCP registry index / fr.scoreconso/public
ScoreConso — service documentaire
fr.scoreconso/public in the official MCP registry.
Endpoint https://scoreconso.fr/mcp.
The registry describes it as: Service public documentaire ScoreConso en lecture seule (guides, statuts, contenus vérifiés).
We read its 18 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
scoreconso_render_case_cockpit scoreconso_route_case scoreconso_route_guarantee_case scoreconso_route_advance_payment_case scoreconso_route_subscription_case scoreconso_route_marketplace_case scoreconso_route_payment_fraud_case scoreconso_get_rule scoreconso_check_deadline scoreconso_score_dossier scoreconso_score_offer_transparency scoreconso_get_evidence_checklist scoreconso_build_action_plan scoreconso_get_template scoreconso_lookup_product_recall scoreconso_lookup_enterprise_identity scoreconso_match_enterprise_mediator_evidence scoreconso_lookup_mediator_reference
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/fr-scoreconso-public)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.