Stream Estate

estate.streamPublished by stream.estateOfficial publisherv2.0.1Updated Oct 24, 2026

French real estate listings, market data and property alerts (Stream Estate API v2).

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server giving an assistant access to French real estate listings, market data and property alerts through the Stream Estate API v2.

What you can do
Search and browse French real estate listings and property details through the Stream Estate API v2, as described in the registry entry. Retrieve market data for properties and areas. Work with property alerts. The manifest lists no individual tools, so the exact set of actions is not documented here.
When to use it
Useful when you want an assistant to look up French property listings, compare market data, or manage property alerts without leaving the conversation.
Requirements
A remote Stream Estate endpoint at api-v2.stream.estate over streamable HTTP. Authentication is required: OAuth plus a Stream Estate API key sent in the X-API-KEY header, created through a Stream Estate signup. Network access is needed.
Before you install
You must supply a Stream Estate API key, a secret credential; keep it private and scope it as narrowly as the service allows. The server is remote, so queries and any data you send go to Stream Estate. Actions on alerts may create, change or delete saved data. No tool list is published, so confirm what it can write before use.

Installation

In SourceWeft

  1. Open Stream Estate 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/estate.stream%2Fmcp/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": {
    "stream-estate": {
      "type": "http",
      "url": "https://api-v2.stream.estate/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

2
  1. v2.0.1LatestOct 9, 2026
  2. v2.0.0Sep 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.

Other Stream integrations