Ext Ops Panel
Open dashboard
Comparison

lotlytics vs DistrictAPI

lotlytics is a plugin bundle for AI coding tools published by daejung83. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). DistrictAPI is an MCP server published by districtapi.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplacelotlyticsDistrictAPI
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
Downloads/month (PyPI): 197
Downloads/week (PyPI): 53
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

lotlytics vs DistrictAPI
FactlotlyticsDistrictAPI
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (lotlytics-mcp-production.up.railway.app/sse)On your machine (districtapi-mcp)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)7Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/daejung83/lotlytics-plugingithub.com/districtapi/districtapi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

lotlytics

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

Real estate market intelligence — investment scores, rental yields, and market data for 895 US metros. Free for top 50 markets.

DistrictAPI

In its own words, on Official MCP Registry:

US public school districts and schools by address — enrollment, demographics, boundaries

How to run each

lotlytics As a Claude Code plugin

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

DistrictAPI As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DISTRICTAPI_KEY=<YOUR_DISTRICTAPI_KEY>" --transport stdio districtapi-mcp -- uvx districtapi-mcp

Requires: DISTRICTAPI_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 lotlytics publish no settings it asks for, so we do not compare settings.

What it can do: lotlytics · What it can do: DistrictAPI · 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