mcpbeat Sign in

Realestate Pro MCP Server

answering

Realestate Pro is answering right now. Last checked 6 min ago.

Czech distress real estate — paid tier (full search, owner data, RUIAN).

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
224 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Realestate Pro every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add realestate-pro --transport http https://realestate-pro.cz-agents.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "realestate-pro": {
      "url": "https://realestate-pro.cz-agents.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.realestate-pro]
url = "https://realestate-pro.cz-agents.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "realestate-pro": {
      "url": "https://realestate-pro.cz-agents.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "realestate-pro": {
      "url": "https://realestate-pro.cz-agents.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://realestate-pro.cz-agents.dev/mcp streamable-http needs auth 216 ms 6 min ago

Alternatives to Realestate Pro

same job, measured the same way
Realestate
by cz-agents

Czech distressed real estate — anonymized district aggregates (k≥5). Free tier.

62 installs/wk 1 tools answering
Real Estate MCP Server
by thenextgennexus

Search properties via Redfin and Google Maps real estate data

19 installs/wk local only
Parceled
by parceled

Real estate data for AI agents: US parcel boundaries (tiles), owners, sale history, permits, hail.

answering
DealScanner
by dealscanner

Search real-estate deals, rank top areas, run rental/BRRRR/flip analysis, pull sold comps.

7 tools answering
x402 government-data search
by lspain1994

Search five paid x402 government-data APIs (IRS, FDA, SSA, HCAD); full records paid over x402.

80 installs/wk local only
Real Estate Data
by dwelldata

DwellData: typed US real-estate feeds — deals, distress, auctions, leads, address lookup.

2 tools answering
Arxiv MCP Server
by cyanheads

Search arXiv, fetch paper metadata, and read full-text content.

596 installs/wk 4 tools answering
Searchapi
by searchapi

Give AI assistants access to real-time search data through SearchApi.

answering

Realestate Pro — questions

Answers built from our own checks of this server.

Why is there no tool list for Realestate Pro?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Realestate Pro working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 224 ms. The bar chart above shows every period we have measured.
How do I connect Realestate Pro?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Realestate Pro need an API key?
Yes. Every time we knock, Realestate Pro answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Realestate Pro?
It answers our handshake in 224 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.