mcpbeat

Borough NYC Real Estate API MCP Server

app.qwady/borough
answering

Borough NYC Real Estate API is answering right now. Last checked 1 min ago. 85 installs a week from npm.

Search NYC rentals and sales, property details, building data, and market analytics

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 148 · avg 15 · -60% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
515 ms
Response time
average over 24h
85
Installs / week
npm and PyPI

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://borough.qwady.app/mcp streamable-http needs key 509 ms 1 min ago

Borough NYC Real Estate API — questions

Answers built from our own checks of this server.

Why is there no tool list for Borough NYC Real Estate API?
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 Borough NYC Real Estate API 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 515 ms. The bar chart above shows every period we have measured.
Is Borough NYC Real Estate API still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Borough NYC Real Estate API?
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 key or an OAuth login: it refuses anonymous clients.
Does Borough NYC Real Estate API need an API key?
Yes. Every time we knock, Borough NYC Real Estate API 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 Borough NYC Real Estate API?
It answers our handshake in 515 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Borough NYC Real Estate API?
The npm package @borough/mcp was installed 85 times in the last week. Week over week that is -60%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.