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.

Real Estate Mcp

REMOTE · REAL_ESTATE_MCP.MCPIZE.RUN · SCANNED SEP 20

MCP server for Real Estate

Available components

remote · real_estate_mcp.mcpize.run 20
0 this week 20 Trust /100
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 Security51
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 Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 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 Real Estate Mcp server?

Real Estate Mcp is a hosted endpoint at https://real_estate_mcp.mcpize.run/mcp, 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 · real_estate_mcp.mcpize.run

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

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.

  • 26 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
  • 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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 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
  • 28 Jul 26 0
    • HTTPS: pass → unverified ▼ security
    • HSTS header: unverified → pass ▲ security
    • Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 500. security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
  • 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 0

    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 · Probed https://real_estate_mcp.mcpize.run/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcpize.run CN=WE1,O=Google Trust Services,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA256 a3038f44f6c701e6132b8002f61f05c0
SANs: mcpize.run, *.mcpize.run
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of real_estate_mcp.mcpize.run. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
run. present 37315 8 Verified
mcpize.run. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 500
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://real_estate_mcp.mcpize.run/mcp HTTP error 500
http (plaintext) http://real_estate_mcp.mcpize.run/mcp Inconclusive 500
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 Real Estate Mcp server?

Real Estate Mcp is listed in the public MCP registry as io.github.varvararatta/real_estate_mcp. MCP server for Real Estate. This page covers its hosted endpoint (https://real_estate_mcp.mcpize.run/mcp).

Is the Real Estate Mcp server safe to use?

Real Estate Mcp scores 20 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 Real Estate Mcp server require authentication?

No. We connected to Real Estate Mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Real Estate Mcp server still maintained?

Real Estate Mcp 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.