Mcp Atlas

io.github.urbankitstudiov0.2.22更新於 Oct 10, 2026

Owner and APN lookup across 286 US counties (297 ArcGIS endpoints). No API key needed.

概覽

AI 產生的概覽

查詢美國縣級地塊 GIS 端點,並為 286 個郡產生 ArcGIS 所有權人搜尋查詢 URL。

功能
以內嵌的 286 個美國郡、297 個 ArcGIS REST 端點圖集提供四個工具。list_counties 顯示涵蓋哪些郡以及當地是否支援所有權人搜尋;find_county 可模糊比對部分名稱、詞組或 FIPS 代碼;get_parcel_endpoint 傳回某個郡的端點 URL、圖層、可搜尋欄位與範例查詢;build_owner_query 傳回可用部分名稱搜尋該郡所有權人/納稅人欄位的可執行 URL。它從不執行查詢,也不傳回地塊紀錄,只告訴你該抓取哪個 URL。
適用情境
當你需要找到正確的縣級地塊 GIS 服務,或在不了解 ArcGIS REST 慣例的情況下建構所有權人或地塊編號搜尋 URL 時適用。適合產權盡職調查、所有權研究與地塊資料工作,前提是你已知或能說出某個美國郡。
執行需求
透過 stdio 在本機執行,通常使用 npx @urbankitstudio/mcp-atlas 或全域 npm 安裝,因此需要 Node.js 與 npm。未宣告 API 金鑰、帳號、環境變數或標頭。圖集資料內嵌於套件中,啟動時不發出網路請求;抓取傳回的查詢 URL 需要網路存取。
安裝前請注意
此伺服器只產生查詢 URL,抓取由助理或使用者自行完成,產生的請求會送往第三方縣級 ArcGIS 服務。所有權人名稱搜尋會傳回房產所有權資訊,屬於敏感個人資料。README 提到供應鏈掃描器對該套件標記了 eval 使用、無人維護的傳遞相依套件、混合授權,以及網路、檔案系統、環境變數與 shell 存取權限和下載量偏低;作者將其中多數歸因於相依套件或 MCP 正常的 stdio 運作方式。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Atlas,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[Socket Badge]

@urbankitstudio/mcp-atlas

[mcp-atlas MCP server]

Query the parcel ArcGIS REST endpoints of 286 counties across 51 US states (50 states plus DC), 297 endpoints total, for owner, APN and address lookup via the Model Context Protocol (MCP).

An MCP server that gives AI assistants direct access to UrbanKit Studio's atlas of manually verified county parcel GIS services. Ask Claude or Cursor to find the ArcGIS REST endpoint for any covered county, get the exact owner-search query URL, and look up parcel data — without needing to know anything about ArcGIS REST API conventions.

Coverage: 286 counties across 51 US states (50 states plus DC), 297 endpoints, 296 of them live (atlas 0.6.25).


Quick start

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "mcp-atlas": {      "command": "npx",      "args": ["-y", "@urbankitstudio/mcp-atlas"]    }  }}

Cursor

Add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json globally):

json
{  "mcpServers": {    "mcp-atlas": {      "command": "npx",      "args": ["-y", "@urbankitstudio/mcp-atlas"]    }  }}

Install globally (optional)

sh
npm install -g @urbankitstudio/mcp-atlas

Then use mcp-atlas as the command instead of npx -y @urbankitstudio/mcp-atlas.


Tools

The four tools are one pipeline, and what separates them is how precisely you can already name the county:

You haveUseYou get
A state, or nothinglist_countiesWhich counties are covered, and whether owner search works there. No URLs.
A vague, misspelled or FIPS referencefind_countyEvery county that reference matches, named, each with its record
An exact state and countyget_parcel_endpointThat one county's endpoint URL, layer, fields and sample query
A county and an owner's namebuild_owner_queryA runnable URL that searches for that name

find_county and get_parcel_endpoint return the same per-county record. They differ in how you address the county: find_county accepts an uncertain reference and may come back with several candidates, get_parcel_endpoint takes an exact pair and answers about one. If you already know the county, skip find_county.

This server never executes a query and returns no parcel records. It tells you the URL to fetch; fetching it is yours to do.

list_counties

Browse coverage. Answers "is this county covered?" and "what can I search there?" — one line per county, with no endpoint URLs or field names.

ParameterTypeRequiredDescription
statestringNoTwo-letter abbreviation (IL) or full name (Illinois)

Example prompt: "List all covered counties in Illinois"

Example output:

ST | County               | Slug                     | Coverage--------------------------------------------------------------------IL | Kane                 | kane-county              | owner+APNIL | Cook                 | cook-county              | APN onlyIL | DuPage               | dupage-county            | owner+APN...

What each Coverage label promises:

LabelMeaning
owner+APNbuild_owner_query returns a URL for at least one endpoint
APN only (county publishes no owner name)A reviewed record says the county serves no usable owner name
location queries onlyNo endpoint answers attribute searches; parcels are reached by geometry, which also returns owner fields
APN only (owner column not searchable)An owner column exists but the county marks it unsearchable by name; a parcel-id or location query returns it
APN onlyNo endpoint documents an owner column

find_county

Resolves a reference you cannot state exactly. Fuzzy-matches a partial or misspelled name, a "County State" phrase, or a 5-digit FIPS code against every covered county, and names each county it matched so an ambiguous reference comes back as a list to choose from. Each match carries that county's record: endpoint URLs, searchable field names, owner field, sample query, license.

ParameterTypeRequiredDescription
querystringYesCounty name (Kane), name+state (Kane IL), or FIPS (17089)

Example prompt: "Find the parcel endpoint for Kane County Illinois"


get_parcel_endpoint

The default lookup once the county is known. Returns the full ArcGIS REST URL, layer index, searchable fields, owner field (or why no owner query is offered), the county's Scope: predicate when the layer is shared statewide or regionally, a generic sample ?where=…&f=json query and the UrbanKit deep-link for one county. For a named owner, use build_owner_query rather than editing the sample query by hand.

ParameterTypeRequiredDescription
statestringYesTwo-letter abbreviation or full name
countystringYesCounty name (Kane or Kane County)

Example prompt: "Give me the ArcGIS REST endpoint for Cook County Illinois"


build_owner_query

The only tool that searches for a named owner. Fills a person or company name into the county's verified owner/taxpayer field as UPPER(field) LIKE UPPER('%NAME%'), a case-insensitive partial match, and returns a URL you can fetch or open. On a shared statewide or regional layer (Connecticut's regional composites, for example) the county's scope predicate is ANDed in front, as (scope) AND UPPER(field) LIKE …, so only that county's rows come back.

An endpoint is refused, with the reason, rather than handed a query that finds nothing or hangs:

  • a reviewed record says the county publishes no usable owner name;
  • the layer serves no attribute search at all (query it by location instead);
  • the owner column is not searchable by name (use a parcel-id or location query).
ParameterTypeRequiredDescription
statestringYesTwo-letter abbreviation or full name
countystringYesCounty name
owner_namestringYesOwner/taxpayer name (partial match)

Example prompt: "Build an ArcGIS query for properties owned by 'Smith' in Kane County IL"

Example output:

County:       Kane, IllinoisOwner field:  TaxNameWHERE clause: UPPER(TaxName) LIKE UPPER('%SMITH%')
Query URL:https://gistech.countyofkane.org/arcgis/rest/services/KanePINList/MapServer/0/query  ?where=UPPER(TaxName)%20LIKE%20UPPER('%25SMITH%25')  &outFields=PIN,TaxName,SiteAddress,SiteCity,MailingAddress  &returnGeometry=false&f=json&resultRecordCount=25

Example conversation

User: I'm doing due diligence on properties in Kane County, Illinois. Can you find all parcels owned by "Blackstone"?

Claude (using mcp-atlas):

  1. Calls get_parcel_endpoint → gets the gistech.countyofkane.org URL and confirms the owner field is TaxName
  2. Calls build_owner_query with owner_name=Blackstone → returns a ready fetch URL
  3. Optionally fetches the URL and formats the parcel results

Atlas coverage

The atlas is maintained by UrbanKit Studio. All endpoints are manually verified. Counties with an owner/taxpayer field support full name-based lookups; PIN-only counties support APN/parcel-number queries.

Full coverage map: https://urbankitstudio.com/parcel-atlas


Data

Atlas data is embedded in the package (no network calls at startup). The underlying @urbankitstudio/atlas SDK is also published separately for programmatic use.


What Socket flags, and how much of it is ours

Socket's supply-chain scanner rates this package in the mid-70s. Clicking through shows a long alert list. Each alert, checked rather than waved away:

AlertWhoseWhat it is
usesEvalNot oursNo eval or new Function anywhere in src/. It comes from a dependency.
unmaintained (21)Not oursTransitive dependencies last published 2017–2021.
mixedLicenseNot oursA dependency published as BSD-3-Clause AND ISC.
noTestsOurs, by designfiles ships dist only. The suite lives in test/ and runs in CI. Shipping tests inside the tarball would be the defect.
networkAccess, filesystemAccess, envVars, shellAccessOursAn MCP server talks to a client over stdio and reads its own config. A server without these could not do the job.
unpopularPackage, noV1OursDownload count and a 0.x version. Both resolve with time, neither is a code issue.

Vulnerability and license both come back at 100, quality at 99. The number the badge shows is the supply-chain sub-score, and its single largest deduction is download count, a popularity measure wearing a security badge's clothes. Judge the list above, not the digit.

The four access alerts are what let the server read its own config and talk to a client over stdio, nothing more. It still never executes a query or returns a parcel record.

License

MIT — © 2026 UrbanKit Studio

來源:README.md,提交 7be3e34

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.2.22最新Oct 10, 2026