# Arcgis Pittsburgh (npm · @pipeworx/mcp-arcgis-pittsburgh)

City of Pittsburgh GIS — Pittsburgh, Pennsylvania open geospatial data (ArcGIS).

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 80/100, [markdown](https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/arcgis-pittsburgh-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/arcgis-pittsburgh-mcp)
- npm · `@pipeworx/mcp-arcgis-pittsburgh`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/pipeworx-mcp-arcgis-pittsburgh.md), [page](https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/pipeworx-mcp-arcgis-pittsburgh)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-arcgis-pittsburgh`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-arcgis-pittsburgh).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 440 tokens (~146/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**: 23/100
  - Stability observed for 7 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 Arcgis Pittsburgh MCP server?

Arcgis Pittsburgh runs locally as an npm package, launched with npx -y @pipeworx/mcp-arcgis-pittsburgh. 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 pipeworx-io-arcgis-pittsburgh -- npx -y @pipeworx/mcp-arcgis-pittsburgh
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-arcgis-pittsburgh": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arcgis-pittsburgh"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-arcgis-pittsburgh": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arcgis-pittsburgh"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-arcgis-pittsburgh -- npx -y @pipeworx/mcp-arcgis-pittsburgh
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-arcgis-pittsburgh": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-arcgis-pittsburgh"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-arcgis-pittsburgh --command npx --arg -y --arg @pipeworx/mcp-arcgis-pittsburgh
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-arcgis-pittsburgh:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-arcgis-pittsburgh"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-arcgis-pittsburgh": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-arcgis-pittsburgh"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-arcgis-pittsburgh -t stdio -c npx -a -y @pipeworx/mcp-arcgis-pittsburgh
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-arcgis-pittsburgh": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-arcgis-pittsburgh"
      ]
    }
  }
}
```

## 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-05 (score 84, +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-03 (score 83, +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-02 (score 82, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 82, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (3)

### `search_datasets` (~130 tokens)

Search City of Pittsburgh GIS open geospatial datasets (parcels, zoning, public works & city services) by keyword. Returns each dataset's name, summary, record_count, owner/org, and its Feature Service `url` — pass that url to query_layer / layer_info.

Input parameters:

- `limit` (number): Max datasets (1-50, default 20).
- `org_id` (string): Optional ArcGIS orgId to override the default (City of Pittsburgh GIS).
- `query` (string): Keyword(s), e.g. "parcels", "crime", "flood zones".

### `query_layer` (~190 tokens)

Query an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like `where`, comma-separated `out_fields`, `order_by`, `limit`, `offset`. Returns attribute rows (and geometry). Use where="1=1" + out_fields="*" to sample.

Input parameters:

- `limit` (number): Max features (1-2000, default 50).
- `offset` (number): Pagination offset.
- `order_by` (string): e.g. "POP DESC".
- `out_fields` (string): Comma-separated field names, or "*" for all (default).
- `url` (string, required): Feature/Map Service layer url ending in /FeatureServer/<n> or /MapServer/<n>.
- `where` (string): SQL where clause, e.g. "STATE = 'CA' AND YEAR >= 2020". Default "1=1".

### `layer_info` (~61 tokens)

Get an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.

Input parameters:

- `url` (string, required): Feature/Map Service layer url, e.g. ".../FeatureServer/0".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/pipeworx-mcp-arcgis-pittsburgh#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 66
- 2026-10-29: 81

## Common questions

### What is the Arcgis Pittsburgh MCP server?

Arcgis Pittsburgh is an MCP server listed in the public MCP registry as io.github.pipeworx-io/arcgis-pittsburgh. City of Pittsburgh GIS, Pittsburgh, Pennsylvania open geospatial data (ArcGIS). This page covers its npm package (@pipeworx/mcp-arcgis-pittsburgh).

### Is the Arcgis Pittsburgh MCP server safe to use?

Arcgis Pittsburgh scores 84 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 Arcgis Pittsburgh MCP server expose?

Arcgis Pittsburgh exposes 3 tools: search_datasets, query_layer, layer_info. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.

### Is the Arcgis Pittsburgh MCP server still maintained?

Arcgis Pittsburgh 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 Arcgis Pittsburgh MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-arcgis-pittsburgh
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-arcgis-pittsburgh
- Repository: https://github.com/pipeworx-io/mcp-arcgis-pittsburgh
- Website: https://pipeworx.io/packs/arcgis-pittsburgh
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/pipeworx-mcp-arcgis-pittsburgh.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/pipeworx-mcp-arcgis-pittsburgh.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-arcgis-pittsburgh/pipeworx-mcp-arcgis-pittsburgh