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.

Election Atlas

REMOTE · ATLAS-PRODUCTION-D344.UP.RAILWAY.APP

US & Canada election maps: precincts, ZIP codes, 2026 districts, ridings. GeoJSON + point lookup.

+3 this week 72 Trust /100

Last scanned (20 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Renamed: use io.github.TaltonFiggins/boundary-atlas (same server, broader scope).

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2974 tokens (~247/item across 12 items; 12 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_officials” rewrote its description, which is the text the model reads security
    • Tool “locate_point” rewrote its description, which is the text the model reads security
    • Schema quality: 224 → 247 ▼ functional
    • Server version: 0.3.0 → 0.4.0 functional
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_officials” rewrote its description, which is the text the model reads security
    • Tool “locate_point” rewrote its description, which is the text the model reads security
    • Tool “search_geographies” rewrote its description, which is the text the model reads security
    • Schema quality: 2324 → 2696 ▼ functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “lookup_address” functional
  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 Nov 26 +1

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

  • 12 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.

  • 10 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.

  • 8 Nov 26 +1
    • Schema quality: 189 → 211 ▼ functional
    • New tool “find_officials” functional
    • Tool “coverage_summary” changed its title: Coverage summary cosmetic
    • Tool “data_freshness” changed its title: Data sources and freshness cosmetic
    • Tool “get_boundaries” changed its title: Get boundaries (GeoJSON) cosmetic
    • Tool “get_geography” changed its title: Get a geography cosmetic
    • Tool “list_children” changed its title: List children cosmetic
    • Tool “list_geographies” changed its title: List geographies cosmetic
    • Tool “locate_point” changed its title: Locate a point cosmetic
    • Tool “nearest_geographies” changed its title: Nearest geographies cosmetic
    • Tool “related_geographies” changed its title: Related geographies (crosswalk) cosmetic
    • Tool “search_geographies” changed its title: Search geographies cosmetic
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 21 Nov 2026 · Probed https://atlas-production-d344.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 618edc56941aa1165ddb080bf9f799eb7c1
SANs: *.up.railway.app, up.railway.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of atlas-production-d344.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
railway.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://atlas-production-d344.up.railway.app/mcp Verified 200
http (plaintext) http://atlas-production-d344.up.railway.app/mcp HTTPS enforced 301 https://atlas-production-d344.up.railway.app/mcp
MCP tools · 12 exposed · ~2,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
coverage_summary ~27

What's in the atlas: row counts by country and level, with the vintage of each layer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

data_freshness ~49

When each upstream dataset was last fetched and checked, what period it describes (vintage), how often it is re-checked, and whether it is overdue. Includes the recent refresh history.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_officials ~581

Who represents a place: members of the U.S. House and Senate, state legislators, the mayor, and the city council member and county supervisor or commissioner where their district maps are on file, with contacts. Give a geography `id` (a congressional district, state, city 'us:place:...', county, town or ZIP 'us:zcta:...') or a point (`lat`, `lon`; for a street address use lookup_address with include_officials=True). For a city, county or ZIP that spans several districts, each representative comes with `share` = share of that area's 2020 residents in the district; for an exact answer use a point. Members listed are those serving now (119th Congress, until January 3, 2027); the districts are the 120th Congress maps elected November 3, 2026. In states that redrew for 2026 (AL, CA, FL, LA, NC, OH, TN, TX, UT) a representative's `note` says they were elected under the previous map. A district with no member is vacant. State legislators (state_legislators=True, except for a whole state, where pass it explicitly) come from Open States; members in states that redrew legislative maps for 2026 (MI, MN, MS) carry a similar note. Mayors (local=True), of cities and, where towns and townships are the local government (NJ, PA, NY, New England, MI, MN, WI), of those too, come from Open States (larger cities, while their term runs) or, failing that, Wikidata (one current head of government, in office since 2010; their `note` says to confirm on the city's website). City council members and county supervisors/commissioners (local=True) come with the largest cities' and counties' own district maps: a point gets the one member for its district (several in multi-member districts); a city id 'us:place:...' or a county id lists the whole body by district; a district id 'us:council_district:...' gives its member. Names are from the city's or county's own GIS layer or official roster, read on the date in `note`; seats chan…

NameTypeReqDescription
id–––
lat–––
localboolean––
lon–––
state_legislatorsboolean––

No output schema declared.

No examples provided.

get_boundaries ~479

Polygon boundaries as a GeoJSON FeatureCollection (EPSG:4326, RFC 7946 winding), for drawing dashboard maps. id: the geography to draw, e.g. 'us:county:34013'. children_level: draw everything at that level inside it instead, e.g. every 'precinct' in a county or state, every 'county' in a state, every 'polling_division' in a riding, or every 'precinct' overlapping a congressional district (any share; use related_geographies for shares). detail: 'high' (~10 m), 'medium' (~50 m, default) or 'low' (~200 m). Neighbouring shapes from the same source share identical edges at every detail level. clip_to_land: trim open water (ocean, bays, Great Lakes) using the state/province shoreline outline (default true; inland lakes are not trimmed; shorelines are generalized to ~1:500k, widened ~200 m so land isn't cut); false gives legal extents. include_districts: add each feature's congressional / state senate / state house district holding the largest share of its population. Feature properties: id, level, code, name, parent_id, region, population (2020 Census for precincts and towns, latest estimate for counties and states), vintage and source_id (2020 Census VTDs have source_id 'us-census-vtd-2020'; current precincts don't), shape_source. Small results come back inline as `geojson`. Larger ones are not returned inline (they'd flood the conversation): the hosted service returns a short-lived `download_url` (fetch it with curl into your project); a local server writes the file to its own export folder and returns `file` (copy it into your project). Page big selections with offset/limit (max 5000 features).

NameTypeReqDescription
children_level–––
clip_to_landboolean––
detailstring––
idstringyes–
include_districtsboolean––
inline_max_kbinteger––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

get_geography ~52

Full record for one geography: attributes, parent chain up to the country, child counts by level, and the source it came from (licence, vintage, last fetched).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

list_children ~77

Geographies directly under `id` (state -> counties and districts, county -> precincts and towns, province -> ridings). Filter with `level`; page with limit/offset (max 1000).

NameTypeReqDescription
idstringyes–
level–––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

list_geographies ~87

Every geography at one level, optionally within one state/province, e.g. all congressional districts in 'NJ' or all federal ridings in 'ON'. Page with limit/offset (max 1000).

NameTypeReqDescription
countrystringyes–
levelstringyes–
limitinteger––
offsetinteger––
region–––

No output schema declared.

No examples provided.

locate_point ~327

Which geographies contain a point: precinct, county, town, city, city council and county board district, congressional and state legislative districts in the US; province, census division and subdivision, federal riding, polling divisions and provincial districts in Canada. Point-in-polygon on stored boundaries (simplified to ~10 m, so a point within ~10 m of a line can land on either side). For a US street address, call lookup_address instead. levels: restrict to some levels (default: all except 'vtd_2020'). If a point is just outside every shape of a level that its state/province has (a pier, a beach, a gap between precinct files), it is matched to the nearest shape of that level in the same state/province within ~1 km and flagged approximate=true with distance_m. not_found lists levels the state/province has data for but no shape here; no_data lists levels with no boundaries there at all (e.g. Nebraska has no state house; Ontario has no provincial polling divisions here). 'council_district' (city council district or ward) and 'county_district' (county supervisor, commissioner or council district) are on file for the largest cities and counties only: elsewhere they come back under not_on_file, which means no map here yet or a body elected at large, not that the point is outside one.

NameTypeReqDescription
latnumberyes–
levels–––
lonnumberyes–

No output schema declared.

No examples provided.

lookup_address ~224

What a US street address is in: its city or town, county, ZIP, congressional and state legislative districts and voting precinct, and optionally who represents it. Give one line with street, city and state: '233 S Wacker Dr, Chicago, IL' (a ZIP helps). The address is matched by the free U.S. Census Geocoder (sent to census.gov, not stored here), then located exactly as locate_point does: the answer has `matched_address`, `lat`, `lon` and the same `results` (pass `levels` to narrow them). include_officials=True adds `officials`, the same list find_officials gives for that point. US addresses only: for Canada, or when you already have coordinates, call locate_point. PO boxes and new construction may not match; then fall back to the ZIP with get_geography('us:zcta:<zip>').

NameTypeReqDescription
addressstringyes–
include_officialsboolean––
levels–––

No output schema declared.

No examples provided.

nearest_geographies ~81

Geographies at `level` whose internal point is closest to (lat, lon). This is a nearest-point approximation, not point-in-polygon. To find the geography containing a point, use locate_point.

NameTypeReqDescription
latnumberyes–
levelstringyes–
limitinteger––
lonnumberyes–

No output schema declared.

No examples provided.

related_geographies ~308

Links between geographies that overlap without nesting, with population shares. Districts: for a precinct, county, town, city (place) or ZIP, the congressional, state senate and state house districts it falls in; for a district, the precincts, counties, towns, cities or ZIPs inside it (filter with `level`, e.g. 'precinct'). A city ('us:place:1714000') also lists its counties. A ZIP ('us:zcta:07102') lists the cities, counties, towns, precincts and districts it overlaps. Ask for `level='zcta'` on a city, county, town or district to list the ZIP codes in it. `weight` is the share of the smaller unit's 2020 population inside the other (for a ZIP, the share of the ZIP's residents in each unit; 0 for parts with land but no residents). relation 'within' means wholly inside (1.0), 'overlaps' means split, 'approximate' means the unit was too small to contain any 2020 block's internal point and was placed by the nearest block. Use min_weight to drop slivers. ZCTAs approximate USPS ZIP Codes.

NameTypeReqDescription
idstringyes–
level–––
limitinteger––
min_weightnumber––
offsetinteger––

No output schema declared.

No examples provided.

search_geographies ~237

Find geographies by name and get their IDs: 'Austin, TX', 'Cook County', '78701', 'Toronto Centre', 'Newark ward 5', or a congressional district as 'TX-21' or "Texas's 21st congressional district". Results are the best name matches, most populous first, as id, level, name, full_name, region and population; call get_geography(id) for the full record. `more` is true when there are further matches: add the state ('Springfield, MO') or a filter. country: 'US' or 'CA'. level: one of the levels from coverage_summary (e.g. 'place', 'county', 'zcta', 'congressional_district', 'federal_electoral_district'). region: USPS state or province code ('NJ', 'ON'). This searches names, not street addresses: for an address call lookup_address.

NameTypeReqDescription
country–––
level–––
limitinteger––
querystringyes–
region–––

No output schema declared.

No examples provided.

Install

How do I install the Election Atlas MCP server?

Election Atlas is a hosted endpoint at https://atlas-production-d344.up.railway.app/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.

remote · atlas-production-d344.up.railway.app

# add to Claude Code
claude mcp add --transport http taltonfiggins-election-atlas 'https://atlas-production-d344.up.railway.app/mcp'
Common questions

What is the Election Atlas MCP server?

Election Atlas is an MCP server listed in the public MCP registry as io.github.TaltonFiggins/election-atlas. US & Canada election maps: precincts, ZIP codes, 2026 districts, ridings. GeoJSON + point lookup. This page covers its hosted endpoint (https://atlas-production-d344.up.railway.app/mcp).

Is the Election Atlas MCP server safe to use?

Election Atlas scores 72 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 Election Atlas MCP server expose?

Election Atlas exposes 12 tools: search_geographies, get_geography, related_geographies, list_children, list_geographies, and 7 more. Their descriptions and schemas cost roughly 2,529 tokens of context every time the server is loaded.

Does the Election Atlas MCP server require authentication?

No. We connected to Election Atlas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Election Atlas MCP server still maintained?

Election Atlas is marked deprecated 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 Election Atlas MCP server?

VerifyMCP ran 13 checks on Election Atlas, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.