Home / MCP registry index / fr.outilsia/local-ai-advisor

OutilsIA — Conseiller IA locale

fr.outilsia/local-ai-advisor in the official MCP registry. Endpoint https://outilsia.fr/mcp.

The registry describes it as: Read-only local AI advice, shared reports and website audits. No PC scan or local actions.

We read its 15 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

check_pc_for_local_ai analyze_shared_report simulate_hardware_upgrade lookup_local_model list_models_for_budget list_installed_models_from_report list_benchmark_proofs_from_report explain_bottleneck list_first_party_measurements recommend_runtime geo_audit explain_geo_audit_method geo_kit explain_local_action_boundary render_machine_cockpit

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/fr-outilsia-local-ai-advisor/badge.svg)](https://lazaretto.dev/mcp-registry/fr-outilsia-local-ai-advisor)

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.