_ registry / mcp streamable-http · checked 1h ago

french-due-diligence

https://mcp-fr.opendata-apis.workers.dev

Registry code: e45ed356d1e6e2d9

api record

Free, keyless French company checks (Sirene, RNE, BODACC) and DPE rental compliance

from a public catalogue that lists it, not from the operator

endpoint
https://mcp-fr.opendata-apis.workers.dev/mcp
protocol
streamable-http ·2025-06-18
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 french-due-diligence live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is french-due-diligence free to use?
Yes — the hub reached it with no key and no payment.
What tools does french-due-diligence have?
6 tools: get_establishment, validate_identifier, search_companies, get_company, get_dpe, check_rental_compliance.
Is french-due-diligence 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
774ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • get_establishment unknown never probed

    One establishment of a French company by SIRET: address, NAF activity, open or closed, head office or not. Use it to check a supplier's or invoice's address.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "siret"
      ],
      "properties": {
        "siret": {
          "type": "string"
        }
      }
    }
    arguments 12 lines
  • validate_identifier unknown never probed

    Checks a French SIREN (9 digits), SIRET (14 digits) or intra-EU VAT number (FR + 11 characters): format, checksum, and whether the registered company or establishment exists. Use it first when an identifier was typed by a person.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 32,
          "minLength": 9,
          "description": "SIREN, SIRET or FR VAT number; spaces allowed"
        }
      }
    }
    arguments 15 lines
  • search_companies unknown 1h ago

    Finds French companies by name, optionally narrowed by department (e.g. 75, 2A, 971), postal code or NAF activity code (e.g. 10.71C). Returns up to 10 companies with their SIREN. Use get_company next for the full profile.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 3,
          "description": "Company name, 3 characters minimum"
        },
        "department": {
          "type": "string",
          "pattern": "^(\\d{2}|2[AB]|9[78]\\d)$"
        },
        "postal_code": {
          "type": "string",
          "pattern": "^\\d{5}$"
        },
        "activity_code": {
          "type": "string",
          "pattern": "^\\d{2}\\.?\\d{2}[A-Za-z]$",
          "description": "NAF rév. 2 code"
        }
      }
    }
    arguments 25 lines
  • get_company unknown 1h ago

    Profile of a French company by SIREN: legal name and form, activity, active or ceased, head office, officers (name and role), whether an insolvency proceeding is ongoing (in_insolvency) and its latest BODACC court announcements. Use it to answer 'can I do business with this company?'.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string"
        }
      }
    }
    arguments 12 lines
  • get_dpe unknown never probed

    The dwelling of a French DPE (energy performance certificate) by its 13-character number (e.g. 2569E0160739C), with the same rental verdict as check_rental_compliance. Replaced DPEs are not available: the ADEME dataset drops them.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dpe_number"
      ],
      "properties": {
        "dpe_number": {
          "type": "string"
        }
      }
    }
    arguments 12 lines
  • check_rental_compliance unknown 1h ago

    For a French postal address, returns each dwelling's energy performance certificate (DPE) and its rental verdict under the Climate and Resilience law: rentable now or not, rent frozen or not, ban date (G 2025, F 2028, E 2034), DPE validity, and the label estimated under current electricity rules. Narrow with floor, surface or address complement. Information, not legal advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address"
      ],
      "properties": {
        "floor": {
          "type": "integer",
          "maximum": 100,
          "minimum": 0
        },
        "address": {
          "type": "string",
          "maxLength": 200,
          "minLength": 5,
          "description": "Full address with house number, postcode and town"
        },
        "surface": {
          "type": "number",
          "maximum": 10000,
          "description": "Living area in m²",
          "exclusiveMinimum": 0
        },
        "complement": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "e.g. 'Apt 12', 'Bât B'"
        }
      }
    }
    arguments 32 lines
_ try it 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 e45ed356d1e6e2d9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e45ed356d1e6e2d9/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/e45ed356d1e6e2d9/badge.svg)](https://brick.blue/agent/e45ed356d1e6e2d9?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 know
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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.