Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.mathieuberthet/mb-mastering

REMOTE · MCP.MATHIEUBERTHET.COM · SCANNED AUG 3

Studio de mastering MB Mastering (Paris) : services, tarifs, infos studio, FAQ et demande de devis.

+1 this week 66 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 583 tokens (~53/item across 11 items; 7 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.mathieuberthet.com

# add to Claude Code
claude mcp add --transport http com-mathieuberthet-mb-mastering https://mcp.mathieuberthet.com/
# ~/.codex/config.toml
[mcp_servers.com-mathieuberthet-mb-mastering]
url = "https://mcp.mathieuberthet.com/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mathieuberthet-mb-mastering": {
      "type": "remote",
      "url": "https://mcp.mathieuberthet.com/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mathieuberthet-mb-mastering --url https://mcp.mathieuberthet.com/ --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-mathieuberthet-mb-mastering:
    url: "https://mcp.mathieuberthet.com/"
// mcp.json
{
  "mcpServers": {
    "com-mathieuberthet-mb-mastering": {
      "type": "http",
      "url": "https://mcp.mathieuberthet.com/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.mathieuberthet.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.mathieuberthet.com CN=YE2,O=Let's Encrypt,C=US 16 Jun 2026 14 Sept 2026 ECDSA 256 ECDSA-SHA384 5a59b9f02c9b33472d45250134501d527e9
SANs: mcp.mathieuberthet.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of mcp.mathieuberthet.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mathieuberthet.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.mathieuberthet.com/ Verified 200
http (plaintext) http://mcp.mathieuberthet.com/ HTTPS enforced 301 https://mcp.mathieuberthet.com/index.php
MCP tools — 7 exposed · ~481 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
fetch ~64

Récupère le contenu complet d'un document MB Mastering à partir de son id (obtenu via search). / Fetches the full content of a document by id (from search results).

NameTypeReqDescription
idstringyesIdentifiant du document renvoyé par search.

No output schema declared.

No examples provided.

get_faq ~41

Réponses aux questions fréquentes sur le mastering chez MB Mastering : prix, délais, révisions, travail à distance, gravure vinyle, localisation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pricing ~36

Donne les tarifs de mastering de MB Mastering, ainsi que les délais, la politique de révisions et les modalités de paiement.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_services ~46

Liste les services de mastering de MB Mastering (mastering stéréo, stems, à distance, gravure vinyle, numérisation, formation) avec leurs tarifs et descriptions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_studio_info ~35

Informations sur le studio MB Mastering : fondateur, expérience, adresse à Paris, équipement analogique, liens et réseaux.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~79

Recherche dans les contenus de MB Mastering (services de mastering, tarifs, studio, FAQ) et renvoie une liste de résultats avec id, titre, extrait et URL. / Searches MB Mastering content (mastering services, rates, studio info, FAQ) and returns matching results.

NameTypeReqDescription
querystringyesTermes de recherche / search query.

No output schema declared.

No examples provided.

send_quote_request ~180

Envoie une demande de devis de mastering à MB Mastering par email. À utiliser quand l'utilisateur souhaite être recontacté. Requiert au minimum le nombre de titres et l'email du demandeur.

NameTypeReqDescription
deadlinestringÉchéance éventuelle.
formatstringSupport final visé (streaming, vinyle, CD…).
genrestringGenre musical.
notesstringPrécisions libres sur le projet.
requester_emailstringyesEmail du demandeur (pour la réponse).
requester_namestringNom du demandeur ou du projet/artiste.
servicestringService souhaité (mastering stéréo, stems, à distance, gravure vinyle…).
titlesintegeryesNombre de titres à masteriser.

No output schema declared.

No examples provided.