_ registry / mcp + a2a JSONRPC · checked 1h ago

boncourant

https://boncourant.fr

Registry code: fc90f51ad221cd67

api record

Serveur public sans authentification. Les calculs directs sont sans état ; create_analysis_study crée un résultat temporaire isolé qui expire sous 24 heures. Aucune action n'est exécutée auprès d'un fournisseur ou d'un compte client.

endpoint
https://boncourant.fr/api/a2a
door code
bd54ba018f44a02a
protocol
JSONRPC ·1.0
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is boncourant live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is boncourant free to use?
Yes — the hub reached it with no key and no payment.
What tools does boncourant have?
2 tools: Évaluer une facture résidentielle structurée, Calculer les tarifs résidentiels.
Is boncourant safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
949ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 739 checks · signed record
  • unknown → live
  • degraded → live
  • unknown → live
_ what it is for
topic
energy & utilities grids & utilities
used for
  • analyze a french electricity bill
  • compare electricity offers with the regulated tariff
  • compute contract renewal notice deadlines
  • check subscribed power level
  • read eex forward power prices
takes → gives
text, data, documents → data, documents
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • bill_audit unknown never probed

    Part.data = {skillId: bill_audit, arguments: schéma analyze_bill de l’OpenAPI}. Recommandation prospective à partir d’une facture déjà extraite ; aucune lecture de PDF ni promesse de récupération d’un trop-perçu. Utiliser les outils MCP dédiés pour les contrôles historiques documentés.

    électricitéfacturerecommandation

  • tariff_comparison unknown never probed

    Part.data = {skillId: tariff_comparison, arguments: schéma simulate de l’OpenAPI}. Consommation, puissance et code postal requis ; part HC déclarée pour HP/HC. Catalogue limité aux offres évaluées, incertitudes et provenance incluses.

    électricitétarifsrésidentiel

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fc90f51ad221cd67.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fc90f51ad221cd67/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fc90f51ad221cd67/badge.svg)](https://brick.blue/agent/fc90f51ad221cd67?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
213ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.