Immo API — DVF immobilier France

app.immoapiPublished by immoapi.appOfficial publisherv1.0.0Updated Oct 28, 2026

Données immobilières DVF France : transactions, comparables GPS et statistiques de marché.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Remote MCP server giving assistants French DVF real-estate data: transactions, GPS-based comparables and market statistics.

What you can do
  • Look up French real-estate transactions from the DVF dataset
  • Find comparable properties by GPS location
  • Retrieve market statistics for an area
  • No tool list is published, so exact operations are not documented; capabilities are inferred from the description.
When to use it
Useful when an assistant needs to answer questions about French property sales, price comparisons near a location, or local market trends, without building a DVF data pipeline yourself.
Requirements
A remote MCP endpoint at immoapi.app over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared. Network access to the provider is needed.
Before you install
Access requires an OAuth sign-in with the provider, so an account and its permissions are involved; check what data the authorization grants. The server is hosted by a third party, so queries and locations you send go to that provider. No tool list is published, so review the tools after connecting before relying on results.

Installation

In SourceWeft

  1. Open Immo API — DVF immobilier France in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.immoapi%2Fimmoapi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "immo-api-dvf-immobilier-france": {
      "type": "http",
      "url": "https://immoapi.app/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.