NYC Property & Venue API

io.github.MatchupLabsPublished by GitHub account MatchupLabsv0.1.2Updated Oct 27, 2026

NYC property intelligence, building violations, and restaurant/venue compliance via MCP.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that gives an assistant NYC property intelligence, building violations, and restaurant or venue compliance data through a hosted API.

What you can do
  • Look up NYC property intelligence and building records
  • Retrieve building violations
  • Check restaurant and venue compliance information
  • Query a hosted NYC data API from the assistant
When to use it
Useful when you need NYC-specific property, building violation, or restaurant and venue compliance information inside an assistant conversation, for example during due diligence, tenant screening, or venue research.
Requirements
Runs as a local stdio process, installed from the npm package @matchuplabs/nyc-api-mcp (Node.js required). Needs an API key from nycapi.app supplied in the NYC_API_KEY environment variable. Optionally set NYC_API_BASE_URL to point at a different API base; the default is Network access to that API is required.
Before you install
Requires a third-party API key (NYC_API_KEY) that is likely tied to a paid account; check pricing and quotas. Queries and the data you look up are sent to the external nycapi.app service, so avoid submitting sensitive information. The manifest lists no tools, so verify the exact capabilities after installing.

Installation

In SourceWeft

  1. Open NYC Property & Venue API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.