Back to Browse

Boncourant MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://boncourant.fr/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

19 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "fr-boncourant-boncourant": {
      "url": "https://boncourant.fr/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Boncourant MCP

Public integration documentation for Boncourant, the French electricity-cost optimizer and auditor. This repository contains documentation and public discovery metadata for the hosted service.

Connect

Add the endpoint as a remote HTTP MCP server in your client. Clients using the mcpServers URL configuration format can use:

{
  "mcpServers": {
    "boncourant": {
      "url": "https://boncourant.fr/mcp"
    }
  }
}

Client configuration formats vary; use your client's remote Streamable HTTP server instructions. No local package or server process is needed.

Capabilities

Start with list_capabilities to discover supported tasks, evidence requirements and limits. The public server exposes 19 tools as of 15 October 2026:

list_capabilities, hc_schedule_change_impact, simulate, analyze_bill, get_methodology, decompose_invoice, annualize_invoice, check_subscribed_power, analyze_renewal_terms, assess_historical_optimality, renewal_advisor, extract_energy_document, run_method, assess_ppa, create_analysis_study, get_analysis_study, get_analysis_report, eex_connector, pro_catalog.

Use the live manifest or MCP tools/list for current schemas. Available checks depend on the supplied evidence. Retrospective billing findings and prospective savings estimates are distinct; incomplete evidence does not establish a billing error or whole-market optimality.

Privacy and boundaries

The public MCP service does not expose private customer accounts, workspaces, Enedis consent, supplier switching or supplier outreach. Direct document extraction is non-retained. Asynchronous studies use opaque receipts; raw input is encrypted until processing ends, then erased, and results expire within 24 hours. Shared-service rate and size limits apply. Review the integration guidance and privacy policy before submitting documents.

Public metadata

server.json is the official registry publication descriptor. discovery.json is a dated snapshot of the public discovery manifest, not a replacement for live discovery. This repository does not contain the hosted application's implementation.

Contact: hello@boncourant.fr.

Version 1.5.1

Adds repository discovery metadata, clearer tool routing, and explicit temporary-study safety and receipt-access documentation. run_method is read-only. Creating an isolated study writes expiring state and may fetch an explicitly supplied document, so it remains non-destructive and idempotent, with readOnlyHint: false and openWorldHint: true. It never changes a customer account or supplier contract.

Reviews

No reviews yet

Be the first to review this server!