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

Boncourant

REMOTE · BONCOURANT.FR · SCANNED SEP 24

Optimiseur et auditeur d'électricité en France : tarifs, contrats, puissance et PPA.

Available components

+3 this week 79 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 2041 tokens (~107/item across 19 items; 18 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Boncourant MCP server?

Boncourant is a hosted endpoint at https://boncourant.fr/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · boncourant.fr

# add to Claude Code
claude mcp add --transport http fr-boncourant-boncourant 'https://boncourant.fr/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fr-boncourant-boncourant": {
      "url": "https://boncourant.fr/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fr-boncourant-boncourant": {
      "type": "http",
      "url": "https://boncourant.fr/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fr-boncourant-boncourant]
url = "https://boncourant.fr/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-boncourant-boncourant": {
      "type": "remote",
      "url": "https://boncourant.fr/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fr-boncourant-boncourant --url 'https://boncourant.fr/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fr-boncourant-boncourant:
    url: "https://boncourant.fr/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fr-boncourant-boncourant": {
      "Transport": "http",
      "Url": "https://boncourant.fr/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fr-boncourant-boncourant -t streamable-http -u 'https://boncourant.fr/mcp'
// mcp.json
{
  "mcpServers": {
    "fr-boncourant-boncourant": {
      "type": "http",
      "url": "https://boncourant.fr/mcp"
    }
  }
}

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.

  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 11 Sept 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.

  • 10 Sept 26 0
    • Stability: unverified → 0.03 functional
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 24 Sept 2026 · Probed https://boncourant.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=boncourant.fr CN=YR2,O=Let's Encrypt,C=US 24 Jul 2026 22 Oct 2026 RSA 2048 SHA256-RSA 5d162df8b4e2f9b5741624aa103996b1efe
SANs: boncourant.fr
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of boncourant.fr. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
boncourant.fr. present 27649 8 Verified
boncourant.fr. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://boncourant.fr/mcp Verified 200
http (plaintext) http://boncourant.fr/mcp HTTPS enforced 308 https://boncourant.fr/mcp
MCP tools · 18 exposed · ~1,938 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_bill ~181

Analyse une facture d'électricité résidentielle déjà extraite (champs structurés) via le moteur versionné. Retourne un verdict explicite stay/switch et l'option tarifaire de chaque offre ; quand aucune offre ne bat le contrat actuel, recommended_offer ne désigne jamais l'offre plus chère du catalogue. MCP est JSON uniquement : extrayez le PDF en amont, puis appelez cet outil avec les champs.

NameTypeReqDescription
conso_annuelle_kwhnumberyes
conso_kwh_hcnumber
conso_kwh_hpnumber
current_annual_cost_eurnumber
current_offerstring
current_supplierstring
optionstring
postal_codestringyes
puissance_kvanumberyes

Structured output declared, but exposes no named fields.

No examples provided.

analyze_renewal_terms ~97

Calcule l'échéance, la date limite de préavis, le dépassement éventuel et l'urgence à partir de clauses déjà extraites. Le type de prix est une valeur canonique, jamais déduit d'un texte libre par cet outil.

NameTypeReqDescription
auto_renewal
end_date
evaluation_datestringyes
notice_period_days
pricing_type

Structured output declared, but exposes no named fields.

No examples provided.

annualize_invoice ~128

Annualise la consommation et/ou le total TTC d'une période avec les coefficients officiels du profil Enedis correspondant au segment, à l'option et à la puissance. Si les coefficients sont indisponibles, le repli linéaire est explicite et borné pour les kWh.

NameTypeReqDescription
optionstring
period_endstringyes
period_kwhnumber
period_startstringyes
period_total_ttc_eurnumber
puissance_kvanumberyes
segmentstringyes

Structured output declared, but exposes no named fields.

No examples provided.

assess_historical_optimality ~83

Compare un contrat signé uniquement aux offres datées, valides et faisables au moment de la signature, sans utiliser d'information postérieure. La conclusion est limitée aux preuves fournies et ne prétend jamais couvrir tout le marché.

NameTypeReqDescription
alternativesarrayyes
contractobjectyes
materiality_eur_yearnumber

Structured output declared, but exposes no named fields.

No examples provided.

assess_ppa ~133

Produit une analyse PPA conditionnelle pour un acheteur, producteur ou prosumer : avantages, risques contractuels, sensibilités économiques fournies par le client, alternatives, liquidité, fiscalité, administration, garanties d'origine et points de négociation. Pour analyser le texte d'un contrat, appelez d'abord extract_energy_document puis transmettez extract.ppa et extract.reading_coverage. Ne présente jamais un scénario comme une prévision ni une orientation générale comme un avis juridique ou fiscal individualisé.

NameTypeReqDescription
contractsarray
customerobjectyes
matched_profileobject

Structured output declared, but exposes no named fields.

No examples provided.

check_subscribed_power ~181

Évalue la puissance à la date demandée sans extrapoler une pointe isolée. Une candidature C5 exige une année de pointes apparentes officielles et les paliers du contrat ; une C4 exige P1 à P4 et reste non concluante si une pointe non étiquetée tombe entre les seuils actifs P1 × 0,93 et P4 × 0,93.

NameTypeReqDescription
available_contract_tiers_kva
connection_segmentstringyes
evaluation_datestringyes
max_demand_kva
max_demand_kw
measurement_basis
measurement_period_days
monthly_max_kva
monthly_max_kw
subscribed_kvanumberyes
subscribed_powers_kva

Structured output declared, but exposes no named fields.

No examples provided.

create_analysis_study ~143

Crée et lance de façon idempotente une étude MCP temporaire pour n’importe quel outil analytique Boncourant pris en charge. Retourne immédiatement un reçu opaque, un statut et une expiration ; utilisez get_analysis_study pour suivre le traitement. L’entrée brute est supprimée à la fin du job et le résultat expire sous 24 heures. Cette opération crée un état temporaire mais n’agit jamais auprès d’un fournisseur ni d’un compte client.

NameTypeReqDescription
argumentsobjectyes
capability_idstring
document_fileobject
idempotency_keystringyes
target_toolstringyes

Structured output declared, but exposes no named fields.

No examples provided.

decompose_invoice ~97

Agrège des lignes de facture déjà extraites en postes canoniques (énergie, TURPE, accise, CTA, TVA, capacité, CEE, frais) et vérifie que leur somme correspond aux totaux HT/TTC déclarés. Retourne la méthode, sa version et le hash des entrées.

NameTypeReqDescription
line_itemsarrayyes
stated_total_ht
stated_total_ttc

Structured output declared, but exposes no named fields.

No examples provided.

eex_connector ~61

Courbe forward EEX France (CAL Y+1, CAL Y+2, M+1). Lit le snapshot public le plus récent depuis market_observation et indique explicitement quand aucune donnée récente n'est disponible.

NameTypeReqDescription
asofstring

Structured output declared, but exposes no named fields.

No examples provided.

extract_energy_document ~114

Extrait en mémoire un PDF ou un texte de facture/contrat via l'extracteur européen, retire les identifiants sensibles de la réponse et lance immédiatement les méthodes déterministes applicables. Le document n'est pas conservé ; les champs incertains exigent confirmation.

NameTypeReqDescription
document_base64string
document_fileobject
document_kindstringyes
document_textstring
evaluation_datestringyes
segmentstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_analysis_report ~55

Retourne le rapport Markdown d’une étude PPA terminée et une URL PDF privée valable deux minutes. Le reçu secret autorise uniquement cette étude et ne doit pas être journalisé ni partagé.

NameTypeReqDescription
receiptstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_analysis_study ~65

Lit l’état queued/running/complete/partial/failed d’une étude temporaire à partir de son reçu secret. Retourne le résultat structuré lorsqu’il est prêt, sans permettre de lister ni d’ouvrir une autre étude.

NameTypeReqDescription
receiptstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_methodology ~74

Retourne la méthodologie de calcul, ses sources, hypothèses et limites. Filtrez par method_id, family ou version pour éviter de charger tout le registre ; sans filtre, retourne le registre complet.

NameTypeReqDescription
familystring
method_idstring
versionstring

Structured output declared, but exposes no named fields.

No examples provided.

list_capabilities ~76

Liste les analyses réellement disponibles, les preuves nécessaires, les livrables, les limites, les méthodes et les prochains outils MCP à appeler. Utilisez cet outil en premier quand la demande porte sur l'électricité en France ou que le bon parcours est incertain.

NameTypeReqDescription
audiencestring
capability_idstring

Structured output declared, but exposes no named fields.

No examples provided.

pro_catalog ~111

Catalogue vérifié des offres d'électricité professionnelles (segment C5, jusqu'à 36 kVA) : nombre d'offres actives, fournisseurs, éventail des prix publiés tout compris, répartition fixe / indexée, date du dernier relevé hebdomadaire. Pour le segment C4 (36 à 250 kVA), retourne le nombre de fournisseurs servis — les prix C4 sont sur devis uniquement. Données relevées chaque semaine auprès du comparateur du Médiateur national de l'énergie.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

renewal_advisor ~167

Joint l'échéance et le préavis du contrat, la courbe EEX CAL Y+1/Y+2 fraîche et le catalogue professionnel comparable. Une courbe stale/partielle ne déclenche jamais de décision, et seuls les prix HT fourniture sont comparés au prix verrouillé HT fourniture.

NameTypeReqDescription
annual_consumption_mwh
auto_renewal
budget_eur_mwh
ceiling_eur_mwh
current_locked_supply_eur_mwhnumberyes
end_date
evaluation_datestringyes
locked_fractionnumber
notice_period_days
pricing_type
segmentstringyes
structure

Structured output declared, but exposes no named fields.

No examples provided.

run_method ~92

Exécute directement une méthode pure publiée par get_methodology avec son JSON Schema, sa version et son hash d'entrée. Les méthodes nécessitant un contexte non sérialisable, comme le calendrier Tempo, sont explicitement refusées.

NameTypeReqDescription
contextobject
inputobjectyes
method_idstringyes
valid_onstring
versionstring

Structured output declared, but exposes no named fields.

No examples provided.

simulate ~80

Simule la facture annuelle d'électricité pour un foyer français. Compare les offres de marché au tarif réglementé et estime les économies potentielles.

NameTypeReqDescription
conso_annuelle_kwhnumberyes
optionstring
postal_codestringyes
proportion_hcnumber
puissance_kvanumberyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Boncourant MCP server?

Boncourant is an MCP server listed in the public MCP registry as fr.boncourant/boncourant. Optimiseur et auditeur d'électricité en France : tarifs, contrats, puissance et PPA. This page covers its hosted endpoint (https://boncourant.fr/mcp).

Is the Boncourant MCP server safe to use?

Boncourant scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Boncourant MCP server expose?

Boncourant exposes 18 tools: list_capabilities, simulate, analyze_bill, get_methodology, eex_connector, and 13 more. Their descriptions and schemas cost roughly 1,938 tokens of context every time the server is loaded.

Does the Boncourant MCP server require authentication?

No. We connected to Boncourant without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Boncourant MCP server still maintained?

Boncourant is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.