Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DistrictAPI

PYPI · DISTRICTAPI-MCP

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

Available components

+15 this week 83 Trust /100

Last scanned (23 hours ago)

Scores higher than 86% of PyPI servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 30 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 443 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 24 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 23 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/districtapi-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~387 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_schools_near_address ~75

Find public schools within a radius of a US street address. Args: address: Full US street address radius_miles: Search radius in miles (default 5.0, max 25.0)

NameTypeReqDescription
addressstringyes–
radius_milesnumber––

No output schema declared.

No examples provided.

get_district ~59

Get full profile for a school district by its NCES LEA ID. Args: nces_id: 7-digit NCES Local Education Agency ID, e.g. "4807380"

NameTypeReqDescription
nces_idstringyes–

No output schema declared.

No examples provided.

get_district_schools ~48

List all schools in a district. Args: nces_id: 7-digit NCES LEA ID of the district

NameTypeReqDescription
nces_idstringyes–

No output schema declared.

No examples provided.

get_school ~46

Get full profile for a school by its NCES school ID. Args: nces_id: 12-digit NCES school ID

NameTypeReqDescription
nces_idstringyes–

No output schema declared.

No examples provided.

lookup_district_by_address ~78

Find the public school district serving a US street address. Returns the district name, NCES ID, state, enrollment, school count, per-pupil expenditure, and demographic breakdown. Args: address: Full US street address, e.g. "1600 Pennsylvania Ave, Austin, TX"

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

search_districts ~81

Search for school districts by name, optionally filtered by state. Args: name: Full or partial district name, e.g. "Austin" or "Austin ISD" state: Two-letter state code to narrow results, e.g. "TX" (optional)

NameTypeReqDescription
namestringyes–
statestring––

No output schema declared.

No examples provided.

Install

How do I install the DistrictAPI MCP server?

DistrictAPI runs locally as a PyPI package, launched with uvx districtapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · districtapi-mcp

# add to Claude Code
claude mcp add dev-districtapi-districtapi-mcp -- uvx districtapi-mcp
Common questions

What is the DistrictAPI MCP server?

DistrictAPI is an MCP server listed in the public MCP registry as dev.districtapi/districtapi-mcp. US public school districts and schools by address, enrollment, demographics, boundaries. This page covers its PyPI package (districtapi-mcp).

Is the DistrictAPI MCP server safe to use?

DistrictAPI scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DistrictAPI MCP server expose?

DistrictAPI exposes 6 tools: lookup_district_by_address, get_district, search_districts, get_district_schools, get_school, find_schools_near_address. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.

Is the DistrictAPI MCP server still maintained?

DistrictAPI is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the DistrictAPI MCP server under?

DistrictAPI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.