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.

io.github.benliberte/immo

NPM · BDATAX-IMMO-MCP · SCANNED SEP 20

InvestScore immobilier France (DPE, DVF, risques, INSEE), payé à la requête en USDC via x402.

Available components

npm · bdatax-immo-mcp 75
+3 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security88
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via x402-fetch > x402 > wagmi > @wagmi/connectors > @metamask/sdk > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 526 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 310 tokens (~155/item across 2 items; 2 tools + 0 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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 io.github.benliberte/immo MCP server?

io.github.benliberte/immo runs locally as an npm package, launched with npx -y bdatax-immo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · bdatax-immo-mcp

# add to Claude Code
claude mcp add benliberte-immo -- npx -y bdatax-immo-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "benliberte-immo": {
      "command": "npx",
      "args": [
        "-y",
        "bdatax-immo-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "benliberte-immo": {
      "command": "npx",
      "args": [
        "-y",
        "bdatax-immo-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add benliberte-immo -- npx -y bdatax-immo-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "benliberte-immo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "bdatax-immo-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add benliberte-immo --command npx --arg -y --arg bdatax-immo-mcp
# ~/.hermes/config.yaml
mcp_servers:
  benliberte-immo:
    command: "npx"
    args: ["-y", "bdatax-immo-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "benliberte-immo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "bdatax-immo-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add benliberte-immo -t stdio -c npx -a -y bdatax-immo-mcp
// mcp.json
{
  "mcpServers": {
    "benliberte-immo": {
      "command": "npx",
      "args": [
        "-y",
        "bdatax-immo-mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 0
    • CVE-2026-67316 no longer affects this package ▲ security
    • CVE-2026-67313 no longer affects this package ▲ security
    • CVE-2026-67312 no longer affects this package ▲ security
    • CVE-2026-67321 no longer affects this package ▲ security
    • CVE-2026-67315 no longer affects this package ▲ security
    • CVE-2026-67320 no longer affects this package ▲ security
    • CVE-2026-67317 no longer affects this package ▲ security
    • CVE-2026-67318 no longer affects this package ▲ security
    • CVE-2026-67319 no longer affects this package ▲ security
    • CVE-2026-67314 no longer affects this package ▲ security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 11 Sept 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 3 Sept 26 67

    First indexed and scored.

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 20 Sept 2026 · Analysed npm/bdatax-immo-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-vcc3-ghjq-m6fr CVE-2026-45822 medium yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-58qx-3vcg-4xpx CVE-2026-45736 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N yes
GHSA-96hv-2xvq-fx4p CVE-2026-48779 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 13
Stale 102
No linked repository 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~310 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
dpe ~145

Récupère le diagnostic de performance énergétique (DPE) d'un bien français, enrichi de la valeur marchande estimée (transactions DVF), des risques naturels et technologiques (Géorisques) et du contexte socio-économique de la commune (INSEE FILOSOFI). Fournir une adresse précise, ou un code postal pour lister les DPE d'une zone. Paiement automatique de 0,001 USDC sur Base (x402).

NameTypeReqDescription
adressestring–Adresse complète, ex: '203 rue Saint-Honoré 75001 Paris'
cpstring–Code postal seul, ex: '75001'

No output schema declared.

No examples provided.

investscore ~165

Analyse d'investissement locatif pour une adresse française. Renvoie deux notes /100 : un RendementScore (potentiel de cash-flow : rendement locatif + contrainte énergétique DPE) et un SécuritéScore (risque Géorisques + liquidité du marché + contexte socio-économique). Croise DPE ADEME, valeur marchande DVF, risques BRGM et revenus INSEE. Paiement automatique de 0,01 USDC sur Base (x402).

NameTypeReqDescription
adressestringyesAdresse complète du bien, ex: '12 rue de la Paix 75002 Paris'
loyerM2Moisnumber–Loyer mensuel au m² si connu (donne un rendement réel au lieu d'estimé)

No output schema declared.

No examples provided.

Common questions

What is the io.github.benliberte/immo MCP server?

io.github.benliberte/immo is an MCP server listed in the public MCP registry as io.github.benliberte/immo. InvestScore immobilier France (DPE, DVF, risques, INSEE), payé à la requête en USDC via x402. This page covers its npm package (bdatax-immo-mcp).

Is the io.github.benliberte/immo MCP server safe to use?

io.github.benliberte/immo scores 75 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.benliberte/immo MCP server expose?

io.github.benliberte/immo exposes 2 tools: investscore, dpe. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.

Is the io.github.benliberte/immo MCP server still maintained?

io.github.benliberte/immo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.benliberte/immo MCP server under?

io.github.benliberte/immo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.