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.

fr.juan-branco/branco

REMOTE · DROIT.JUAN-BRANCO.FR · SCANNED SEP 21

French legal research: statutes in force at any date, case law both ways, verified citations.

+3 this week 85 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 Security91
Transport & Reachability100
Schema Quality & AI Usability65
  • 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
  • Context-footprint check failed: tool/resource definitions use about 1470 tokens (~367/item across 4 items; 3 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 Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 13% of tool parameters carry a description.Partial
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the fr.juan-branco/branco MCP server?

fr.juan-branco/branco is a hosted endpoint at https://droit.juan-branco.fr/api/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 · droit.juan-branco.fr

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

  • 21 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail functional
    • The server now declares the “prompts” capability functional
    • The server now declares the “resources” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “recherche-juridique-branco” functional
    • New resource “methode-juridique-branco” functional
    • Server version: 0.55.4 → 0.55.9 functional
  • 20 Sept 26 0
    • Server version: 0.53.1 → 0.55.4 functional
  • 19 Sept 26 +1

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

  • 17 Sept 26 +1
    • Server version: 0.52.9 → 0.53.1 functional
  • 15 Sept 26 +1
    • Server version: 0.52.7 → 0.52.9 functional
  • 14 Sept 26 0
    • Server version: 0.50.1 → 0.52.7 functional
  • 13 Sept 26 +1
    • Server version: 0.47.1 → 0.50.1 functional
  • 12 Sept 26 0
    • Server version: 0.45.2 → 0.47.1 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 21 Sept 2026 · Probed https://droit.juan-branco.fr/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=droit.juan-branco.fr CN=WE1,O=Google Trust Services,C=US 23 Aug 2026 21 Nov 2026 ECDSA 256 ECDSA-SHA256 16333bdc9345391813bdcb2f8276c9da
SANs: droit.juan-branco.fr
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of droit.juan-branco.fr. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
juan-branco.fr. present 55269 13 Verified
droit.juan-branco.fr. Verified address RRset verified with the apex keys
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), geolocation=(), microphone=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://droit.juan-branco.fr/api/mcp Verified 200
http (plaintext) http://droit.juan-branco.fr/api/mcp HTTPS enforced 302 https://droit.juan-branco.fr/api/mcp
MCP tools · 3 exposed · ~238 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
decrire_etat_corpus ~44

Expose les versions, bornes, compteurs, retards, limites, alvéoles et garde-fou qualité actuellement déclarés par BRANCO.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

rechercher_circulaires_penales ~100

Recherche localement les notices de toutes les circulaires publiées en ligne dans le Bulletin officiel du ministère de la Justice. Le filtre pénal est volontairement large ; une recherche peut aussi porter sur l’ensemble du catalogue ou sur un numéro NOR.

NameTypeReqDescription
limiteinteger
norstring
offsetinteger
perimetrestring
requetestring

Structured output declared, but exposes no named fields.

No examples provided.

verifier_citation ~94

Contrôle localement si une citation figure dans un texte fourni, à l’identique ou après normalisation de la casse, des espaces et signes typographiques. Ne valide ni l’autorité, ni la pertinence, ni le sens juridique.

NameTypeReqDescription
citationstringyes
longueur_contexteinteger
texte_sourcestringyesTexte à vérifier, jamais une pièce ni une donnée confidentielle.
NameTypeReqDescription
empreinte_source_sha256stringyes
explicationstringyes
extraityes
positionyes
statutstringyes

No examples provided.

Common questions

What is the fr.juan-branco/branco MCP server?

fr.juan-branco/branco is an MCP server listed in the public MCP registry as fr.juan-branco/branco. French legal research: statutes in force at any date, case law both ways, verified citations. This page covers its hosted endpoint (https://droit.juan-branco.fr/api/mcp).

Is the fr.juan-branco/branco MCP server safe to use?

fr.juan-branco/branco scores 85 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 fr.juan-branco/branco MCP server expose?

fr.juan-branco/branco exposes 3 tools: verifier_citation, decrire_etat_corpus, rechercher_circulaires_penales. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

Does the fr.juan-branco/branco MCP server require authentication?

Yes. fr.juan-branco/branco asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the fr.juan-branco/branco MCP server still maintained?

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