Ext Ops Panel
Open dashboard
Comparison

jucho-kun vs NYC Property & Venue API

jucho-kun is a plugin bundle for AI coding tools published by pinotan2024-coder. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). NYC Property & Venue API is an MCP server published by MatchupLabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
Marketplacejucho-kunNYC Property & Venue API
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 119
Downloads/week (npm): 30
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

jucho-kun vs NYC Property & Venue API
Factjucho-kunNYC Property & Venue API
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@matchuplabs/nyc-api-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/pinotan2024-coder/jucho-kungithub.com/matchup-labs/nycapi
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

jucho-kun

In its own words, on Claude Code: claude-plugins-community:

Automates the preliminary investigation phase for Japanese real estate disclosure documents (重要事項説明書). Given a property address, it generates a complete due diligence checklist, extracts key facts from PDFs (registry certificates, urban planning maps, hazard maps), and outputs a structured Excel investigation report. Built for licensed real estate appraisers and agents (宅建士・不動産鑑定士).

NYC Property & Venue API

In its own words, on Official MCP Registry:

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

How to run each

jucho-kun As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install jucho-kun@claude-community

NYC Property & Venue API As a local MCP server: npm package

Claude Code
claude mcp add --env "NYC_API_KEY=<YOUR_NYC_API_KEY>" --transport stdio nyc-api -- npx -y @matchuplabs/nyc-api-mcp

Requires: NYC_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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 jucho-kun publish no settings it asks for, so we do not compare settings.

What it can do: jucho-kun · What it can do: NYC Property & Venue API · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built