NYC Property & Venue API vs US Building Permit Aggregator
NYC Property & Venue API is an MCP server published by MatchupLabs. Marketplaces we read that list it: 1 (Official MCP Registry). US Building Permit Aggregator is an MCP server published by dizzyvinci. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  US Building Permit Aggregator | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (npm): 119 Downloads/week (npm): 30 Not marked · First seen |
Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | NYC Property & Venue API | US Building Permit Aggregator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@matchuplabs/nyc-api-mcp) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/matchup-labs/nycapi | github.com/dizzyvinci/apify-foundry |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
NYC Property & Venue API
NYC property intelligence, building violations, and restaurant/venue compliance via MCP.
US Building Permit Aggregator
Pull recent building permits from 9 US cities in a unified schema from official open-data portals.
How to run each
NYC Property & Venue API As a local MCP server: npm package
claude mcp add --env "NYC_API_KEY=<YOUR_NYC_API_KEY>" --transport stdio nyc-api -- npx -y @matchuplabs/nyc-api-mcpRequires: NYC_API_KEY (secret)
US Building Permit Aggregator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only US Building Permit Aggregator has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of US Building Permit Aggregator publish no settings it asks for, so we do not compare settings.
What it can do: NYC Property & Venue API · What it can do: US Building Permit Aggregator · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.