Borough NYC Real Estate API

app.qwadyPublished by qwady.appOfficial publisherv1.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Lets an assistant search NYC rental and sale listings, look up property and building details, and pull market analytics.

What you can do
Borough exposes New York City real estate data to an assistant. According to its registry description, it covers rental and sale listings, property details, building data, and market analytics. The manifest does not list individual tools, so the exact operations are not documented here. It is offered both as a remote endpoint and as a local npm package run with npx.
When to use it
Useful when someone is researching NYC housing: comparing rentals or sales, checking details on a specific property or building, or reviewing neighborhood market trends. Less relevant outside New York City real estate.
Requirements
Either a remote endpoint or a local Node.js runtime to run the npm package with npx. Authentication is required via OAuth, and a Borough API key supplied as the BOROUGH_API_KEY environment variable; the provider states a free key is available. Network access is needed.
Before you install
The server requires an API key (BOROUGH_API_KEY) and OAuth authentication, so treat those credentials as secrets. The provider mentions a pricing page, so paid tiers or usage limits may apply. The manifest does not list tools, so what the server can read or change is not verifiable from the supplied information.

Installation

In SourceWeft

  1. Open Borough NYC Real Estate API 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/app.qwady%2Fborough/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": {
    "borough-nyc-real-estate-api": {
      "type": "http",
      "url": "https://borough.qwady.app/mcp"
    }
  }
}

README

This repository has no README.

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

1
  1. v1.1.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.