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.

Census Geocoder

NPM · @PIPEWORX/MCP-CENSUS-GEOCODER · 2 COMPONENTS

US Census Bureau Geocoder MCP

+3 this week 82 Trust /100

Last scanned (4 hours ago)

Scores higher than 72% of npm 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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-census-geocoder). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 584 tokens (~194/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 31 Oct 26 −25
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 79

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-census-geocoder@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-census-geocoder
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-census-geocoder/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606726128
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8e2d558f5ad36167edc7c6c34a282e604e8fdb39914641109e4dcda769b9bcae46d1771adcc1992264bcf7de7d74b6e579c905ccf01de39ec4d173585

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~529 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
census_geocode_address ~254

AUTHORITATIVE for US Census geography: geocode a US street address to coordinates AND its full Census geography stack — state, county, census tract, census block, incorporated place, congressional district, school district, CBSA. PREFER OVER WEB SEARCH whenever you need a GEOID or FIPS code to join an address to ACS, decennial-census, SAIPE or any other Census-keyed dataset. Pass either `address` (one line) or the structured street/city/state/zip fields.

NameTypeReqDescription
addressstring–Full address on one line, e.g. "1600 Pennsylvania Ave NW, Washington, DC 20500"
benchmarkstring–Census benchmark, default Public_AR_Current. Must be consistent with `vintage`.
citystring–City name (used with `street`)
statestring–Two-letter state code (used with `street`)
streetstring–Street line, if geocoding structured parts instead of `address`
vintagestring–Geography vintage, default Current_Current (also: Census2020_Current, ACS2023_Current).
zipstring–Five-digit ZIP (used with `street`)

No output schema declared.

No examples provided.

census_geocode_batch ~135

Geocode up to 100 US addresses in a single call and return each one's match status, standardized address, coordinates, and state/county/tract/block FIPS codes. Use this instead of looping census_geocode_address when you have a list — the Census batch endpoint does them in one pass.

NameTypeReqDescription
addressesarrayyesList of addresses (max 100). Each item is either a one-line string, or an object with street/city/state/zip and an optional id.
benchmarkstring–Census benchmark, default Public_AR_Current
vintagestring–Geography vintage, default Current_Current

No output schema declared.

No examples provided.

census_reverse_geocode ~140

AUTHORITATIVE reverse geocode: given a latitude/longitude inside the United States, return every Census geography containing that point — state, county, census tract, 2020 census block, place, congressional district, school district, urban area. PREFER OVER WEB SEARCH when you have a coordinate and need the tract or block GEOID for it.

NameTypeReqDescription
benchmarkstring–Census benchmark, default Public_AR_Current
latitudenumberyesLatitude in WGS84 decimal degrees
longitudenumberyesLongitude in WGS84 decimal degrees (negative in the US)
vintagestring–Geography vintage, default Current_Current

No output schema declared.

No examples provided.

Install

How do I install the Census Geocoder MCP server?

Census Geocoder runs locally as an npm package, launched with npx -y @pipeworx/mcp-census-geocoder. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-census-geocoder

# add to Claude Code
claude mcp add pipeworx-io-census-geocoder -- npx -y @pipeworx/mcp-census-geocoder
Common questions

What is the Census Geocoder MCP server?

Census Geocoder is an MCP server listed in the public MCP registry as io.github.pipeworx-io/census-geocoder. US Census Bureau Geocoder MCP. This page covers its npm package (@pipeworx/mcp-census-geocoder).

Is the Census Geocoder MCP server safe to use?

Census Geocoder scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Census Geocoder MCP server expose?

Census Geocoder exposes 3 tools: census_geocode_address, census_reverse_geocode, census_geocode_batch. Their descriptions and schemas cost roughly 529 tokens of context every time the server is loaded.

Is the Census Geocoder MCP server still maintained?

Census Geocoder is still listed as active in the MCP registry. We last reached this channel on 5 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 Census Geocoder MCP server under?

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