# Address to Census Tract MCP (remote · address-to-census-tract-mcp.lipmichal.workers.dev)

US address to census tract, block group, county FIPS and districts, from the Census Geocoder.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `address-to-census-tract-mcp.lipmichal.workers.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp)

## Channel facts

- Endpoint: `https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 495 tokens (~165/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Address to Census Tract MCP server?

Address to Census Tract MCP is a hosted endpoint at https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-address-to-census-tract-mcp 'https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-address-to-census-tract-mcp": {
      "url": "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-address-to-census-tract-mcp": {
      "type": "http",
      "url": "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-address-to-census-tract-mcp]
url = "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-address-to-census-tract-mcp": {
      "type": "remote",
      "url": "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-address-to-census-tract-mcp --url 'https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-address-to-census-tract-mcp:
    url: "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-address-to-census-tract-mcp": {
      "Transport": "http",
      "Url": "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-address-to-census-tract-mcp -t streamable-http -u 'https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-address-to-census-tract-mcp": {
      "type": "http",
      "url": "https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 74, +1)

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

### 2026-11-18 (score 73, +1)

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

### 2026-11-16 (score 72, +1)

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

### 2026-11-14 (score 71, +1)

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

### 2026-11-12 (score 70, +1)

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

### 2026-11-10 (score 69, +1)

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

### 2026-11-07 (score 68, +1)

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

### 2026-11-06 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `get_census_tract_for_address` (~193 tokens)

Get census tract for an address

Look up the census tract for a US street address with the official US Census Bureau Geocoder. Returns the matched address, latitude and longitude, the 11-digit tract GEOID and tract number, block group and block GEOIDs, state and county FIPS, incorporated place, county subdivision, congressional district, state senate and house districts, urban area and combined statistical area. Use it for CRA, LIHTC, opportunity zone, grant eligibility and demographic lookups that start from an address.

Input parameters:

- `address` (string, required): One-line US address with house number, street, city and state or ZIP, for example "1600 Pennsylvania Ave NW, Washington, DC 20500".
- `vintage` (string): Census vintage. current (default) uses today's geographies; census2020 uses the 2020 Census geographies; acs2017 to acs2026 match an ACS release.

### `get_census_tract_for_coordinates` (~120 tokens)

Get census tract for coordinates

Census tract, block group, block, county, place and congressional and state legislative districts for a latitude and longitude, from the US Census Bureau Geocoder.

Input parameters:

- `latitude` (number, required): Latitude, for example 41.8827.
- `longitude` (number, required): Longitude, for example -87.6237.
- `vintage` (string): Census vintage. current (default) uses today's geographies; census2020 uses the 2020 Census geographies; acs2017 to acs2026 match an ACS release.

### `explain_census_geoid` (~113 tokens)

Explain a census GEOID

Split a census GEOID (2 digits state, 5 county, 11 tract, 12 block group, 15 block, or with a 1400000US style prefix) into state and county FIPS, tract code, the tract number as Census displays it (012405 is 124.05), block group and block. No network call.

Input parameters:

- `geoid` (string, required): GEOID, for example "06075012405" or "1400000US06075012405".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 69
- 2026-11-10: 69
- 2026-11-09: 68
- 2026-11-08: 68
- 2026-11-07: 68
- 2026-11-06: 67
- 2026-11-05: 67

## Common questions

### What is the Address to Census Tract MCP server?

Address to Census Tract MCP is listed in the public MCP registry as io.github.theluckystrike/address-to-census-tract-mcp. US address to census tract, block group, county FIPS and districts, from the Census Geocoder. This page covers its hosted endpoint (https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp).

### Is the Address to Census Tract MCP server safe to use?

Address to Census Tract MCP scores 74 out of 100 on VerifyMCP. 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 Address to Census Tract MCP server expose?

Address to Census Tract MCP exposes 3 tools: get_census_tract_for_address, get_census_tract_for_coordinates, explain_census_geoid. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.

### Does the Address to Census Tract MCP server require authentication?

No. We connected to Address to Census Tract MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Address to Census Tract MCP server still maintained?

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

### What did VerifyMCP test on the Address to Census Tract MCP server?

VerifyMCP ran 12 checks on Address to Census Tract MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Address to Census Tract MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://address-to-census-tract-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/address-to-census-tract-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-address-to-census-tract-mcp/address-to-census-tract-mcp
