
BocaRoss MCP server
Which MCP servers are BocaRoss's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namefr.bocaross/annuaireverified in the MCP registry
The registry name sits under bocaross.fr. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools2
- Server calls itselfbocaross
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 468 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- Parameters are untyped or undescribed in 1 of 2 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score98 of 100answers 100 · definitions 92 · context 100 · connects 100
- Answered100% of days7 of 7 daily checks
- Median first answer505 ms
- Space in an agent's context≈ 668 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsA · 92 of 100
- Typed results2 of 2 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 2
What an agent can do with it
- not sure · Book a windscreen replacement with a nearby artisan
- not sure · Get a technical inspection booked without phoning
- cannot · Keep service records and MOT due dates in one place
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
chercher_prosTrouve des professionnels indépendants de l’automobile (garage, carrosserie, pare-brise, contrôle technique, lavage et detailing) autour d’une commune de France, ou autour de l’utilisateur (« près de moi », « autour de moi ») quand…
fiche_proDonne le détail d’un professionnel BocaRoss à partir de son identifiant (le champ « slug » rendu par chercher_pros, ou la fin de l’URL bocaross.fr/pro/…) : coordonnées, horaires des sept jours, prestations avec prix quand ils sont…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"annuaire": {
"type": "http",
"url": "https://bocaross.fr/api/v1/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http bocaross https://bocaross.fr/api/v1/mcpclaude.ai, ChatGPT and other clients: add https://bocaross.fr/api/v1/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.