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.

FlatWay Property Estimator

REMOTE · MCP.FLATWAY.FR · SCANNED AUG 22

French property prices, market trends & live listings for any French address. Powered by DVF data.

Available components

−6 this week 0 Trust /100

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security14
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the FlatWay Property Estimator MCP server?

FlatWay Property Estimator is a hosted endpoint at https://mcp.flatway.fr/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.flatway.fr

# add to Claude Code
claude mcp add --transport http lfaykus-flatway-estimate 'https://mcp.flatway.fr/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "lfaykus-flatway-estimate": {
      "url": "https://mcp.flatway.fr/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lfaykus-flatway-estimate": {
      "type": "http",
      "url": "https://mcp.flatway.fr/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.lfaykus-flatway-estimate]
url = "https://mcp.flatway.fr/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lfaykus-flatway-estimate": {
      "type": "remote",
      "url": "https://mcp.flatway.fr/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lfaykus-flatway-estimate --url 'https://mcp.flatway.fr/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  lfaykus-flatway-estimate:
    url: "https://mcp.flatway.fr/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lfaykus-flatway-estimate": {
      "Transport": "http",
      "Url": "https://mcp.flatway.fr/sse"
    }
  }
}
# add to Vellum
assistant mcp add lfaykus-flatway-estimate -t streamable-http -u 'https://mcp.flatway.fr/sse'
// mcp.json
{
  "mcpServers": {
    "lfaykus-flatway-estimate": {
      "type": "http",
      "url": "https://mcp.flatway.fr/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 22 Aug 26 −6

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 4

    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 22 Aug 2026 · Probed https://mcp.flatway.fr/sse

TLS unreached
DNSSEC secure

Validation of mcp.flatway.fr. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
flatway.fr. present 47981 8 Verified
mcp.flatway.fr. Verified address RRset verified with the apex keys
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.flatway.fr/sse Unreachable
http (plaintext) http://mcp.flatway.fr/sse HTTPS enforced
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the FlatWay Property Estimator MCP server?

FlatWay Property Estimator is an MCP server listed in the public MCP registry as io.github.Lfaykus/flatway-estimate. French property prices, market trends & live listings for any French address. Powered by DVF data. This page covers its hosted endpoint (https://mcp.flatway.fr/sse).

Is the FlatWay Property Estimator MCP server safe to use?

FlatWay Property Estimator scores 0 out of 100 on VerifyMCP. 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.

Does the FlatWay Property Estimator MCP server require authentication?

Its publisher declares no required credentials for FlatWay Property Estimator. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the FlatWay Property Estimator MCP server still maintained?

FlatWay Property Estimator has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.