Home / MCP registry index / com.mathieuberthet/mb-mastering
com.mathieuberthet/mb-mastering
com.mathieuberthet/mb-mastering in the official MCP registry.
Endpoint https://mcp.mathieuberthet.com/.
The registry describes it as: Studio de mastering MB Mastering (Paris) : services, tarifs, infos studio, FAQ et demande de devis.
We read its 20 tools on 2026-10-27. 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
search fetch get_services get_pricing get_studio_info get_faq send_quote_request prepare_quote_email qonto_create_invoice qonto_create_quote qonto_list qonto_get qonto_delete imap_list_inbox imap_get_mail list_quote_requests qonto_append_invoice_line qonto_finalize_invoice qonto_update_client upload_master
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-mathieuberthet-mb-mastering)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.