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

openbase-mcp

https://openbase.fr

Registry code: 139545fdee9aff2f

api record

OpenBase expose les données publiques officielles des entreprises françaises.

Méthode recommandée : commencez par `recherche_entreprise` ou `autocomplete` pour obtenir un SIREN, puis utilisez ce SIREN avec les autres outils — ne consommez pas un appel de recherche si vous avez déjà le SIREN.

endpoint
https://openbase.fr/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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
113ms

last good check

priced tools
0

of 14 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 14 tools
14 never probed 0 of 14 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.

  • autocomplete unknown 3h ago

    Recherche de noms ou identifiants, jusqu’à 10 résultats. Aucun engagement de latence.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Préfixe de recherche (min 2 caractères)"
        }
      }
    }
    arguments 12 lines
  • marches_publics unknown never probed

    Attributions référencées dans les données de commande publique, jusqu’à 20 résultats.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Nom de l'entreprise"
        },
        "limit": {
          "type": "number",
          "description": "Nombre de résultats (max 20)"
        },
        "siren": {
          "type": "string",
          "description": "SIREN (optionnel, pour filtrer précisément)"
        }
      }
    }
    arguments 20 lines
  • fiche_entreprise unknown never probed

    Identité, mandats diffusables, dernier bilan disponible, annonces BODACC et établissements. Des champs peuvent manquer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string",
          "description": "Numéro SIREN (9 chiffres)"
        }
      }
    }
    arguments 12 lines
  • recherche_entreprise unknown never probed

    Recherche par nom, SIREN ou SIRET : jusqu’à 10 résultats disponibles.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Nom d'entreprise, raison sociale, SIREN (9 chiffres) ou SIRET (14 chiffres)"
        }
      }
    }
    arguments 12 lines
  • recherche_dirigeant unknown never probed

    Recherche de mandats déclarés par nom, avec résultats limités et homonymies possibles.

    mcp-tool

    {
      "type": "object",
      "required": [
        "nom"
      ],
      "properties": {
        "nom": {
          "type": "string",
          "description": "Nom complet ou patronyme du dirigeant"
        }
      }
    }
    arguments 12 lines
  • bodacc unknown never probed

    Jusqu’à 20 annonces BODACC disponibles, datées de leur publication.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string",
          "description": "Numéro SIREN"
        }
      }
    }
    arguments 12 lines
  • classement_entreprises unknown never probed

    Classement limité à 50 entreprises par CA, effectif disponible ou création ; filtres département et catégorie.

    mcp-tool

    {
      "type": "object",
      "required": [
        "type"
      ],
      "properties": {
        "type": {
          "enum": [
            "ca",
            "effectif",
            "creation"
          ],
          "type": "string",
          "description": "Critère de tri"
        },
        "limit": {
          "type": "number",
          "description": "Nombre de résultats (max 50, défaut 20)"
        },
        "categorie": {
          "enum": [
            "GE",
            "ETI",
            "PME",
            "TPE"
          ],
          "type": "string",
          "description": "Catégorie INSEE. Optionnel."
        },
        "departement": {
          "type": "string",
          "description": "Code département (ex: 75, 13, 971). Optionnel."
        }
      }
    }
    arguments 35 lines
  • entreprises_par_secteur unknown never probed

    Jusqu’à 50 entreprises actives d’un code NAF, avec filtre département facultatif. Résultat non exhaustif.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code_naf"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Nombre de résultats (max 50, défaut 20)"
        },
        "code_naf": {
          "type": "string",
          "description": "Code NAF/APE (ex: 62.01Z, 47.11D)"
        },
        "departement": {
          "type": "string",
          "description": "Département facultatif"
        }
      }
    }
    arguments 20 lines
  • decisions_justice unknown never probed

    Recherche de décisions disponibles par nom ou sujet, jusqu’à 20 résultats. Une absence ne prouve pas l’absence de contentieux.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Nom d'entreprise, SIREN, ou sujet juridique"
        },
        "limit": {
          "type": "number",
          "description": "Nombre de résultats (max 20)"
        }
      }
    }
    arguments 16 lines
  • reseau_capitalistique unknown never probed

    Réseau de mandats de personnes morales sur 1 à 2 niveaux. Les liens ne prouvent pas la détention du capital.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string",
          "description": "Numéro SIREN"
        },
        "profondeur": {
          "type": "number",
          "description": "Profondeur de remontée (1 = direct, 2 = 2 niveaux, max 2). Défaut 1."
        }
      }
    }
    arguments 16 lines
  • signaux_business unknown never probed

    Événements référencés : offres rattachées, marchés, capital, aides, certifications et risques. Couverture partielle et datée.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string",
          "description": "Numéro SIREN"
        }
      }
    }
    arguments 12 lines
  • surveiller_entreprise unknown never probed

    Ajoute une entreprise au suivi du titulaire de la clé. Clé MCP Pro activée depuis un compte connecté et abonnement Surveillance actif requis, dans sa limite. Contrôle quotidien, événements détectés selon les sources disponibles.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Adresse du titulaire de la clé uniquement (facultatif)"
        },
        "siren": {
          "type": "string",
          "description": "Numéro SIREN à surveiller"
        },
        "events": {
          "type": "array",
          "items": {
            "enum": [
              "bodacc",
              "dirigeant",
              "capital",
              "procedure_collective",
              "certification"
            ],
            "type": "string"
          },
          "description": "Ne pas renseigner : le filtrage par catégorie via MCP n’est pas pris en charge."
        }
      }
    }
    arguments 30 lines
  • apercu_solvabilite unknown 3h ago

    Score OpenBase indicatif et ratios du dernier bilan disponible. Aucune probabilité de défaut garantie.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string",
          "description": "Numéro SIREN"
        }
      }
    }
    arguments 12 lines
  • bilans_financiers unknown 3h ago

    Dernier exercice disponible sans clé ; historique via comptes_annuels sur le serveur identifié, selon disponibilité.

    mcp-tool

    {
      "type": "object",
      "required": [
        "siren"
      ],
      "properties": {
        "siren": {
          "type": "string",
          "description": "Numéro SIREN"
        }
      }
    }
    arguments 12 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, it shows the verified badge, 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 139545fdee9aff2f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/139545fdee9aff2f/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/139545fdee9aff2f/badge.svg)](https://brick.blue/agent/139545fdee9aff2f)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

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