# PortlandMaps (Unofficial) (remote · portlandmaps-mcp.vercel.app)

Unofficial MCP server for the public PortlandMaps property/permit/zoning API. Not city-affiliated.

- Trust score: 72/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `portlandmaps-mcp.vercel.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/mcp-v2.md), [page](https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/mcp-v2)
- npm · `portlandmaps-mcp`: 30/100, [markdown](https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/portlandmaps-mcp.md), [page](https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/portlandmaps-mcp)

## Channel facts

- Endpoint: `https://portlandmaps-mcp.vercel.app/mcp/v2`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.5`

## 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-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 60/100
  - 80% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3314 tokens (~276/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
  - Structured output schemas are declared (9% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http gptnowllc-portlandmaps-mcp https://portlandmaps-mcp.vercel.app/mcp/v2
```

### Codex

```toml
[mcp_servers.gptnowllc-portlandmaps-mcp]
url = "https://portlandmaps-mcp.vercel.app/mcp/v2"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gptnowllc-portlandmaps-mcp": {
      "type": "remote",
      "url": "https://portlandmaps-mcp.vercel.app/mcp/v2",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gptnowllc-portlandmaps-mcp --url https://portlandmaps-mcp.vercel.app/mcp/v2 --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gptnowllc-portlandmaps-mcp:
    url: "https://portlandmaps-mcp.vercel.app/mcp/v2"
```

### Other

```json
{
  "mcpServers": {
    "gptnowllc-portlandmaps-mcp": {
      "type": "http",
      "url": "https://portlandmaps-mcp.vercel.app/mcp/v2"
    }
  }
}
```

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-08-03 (score 72, +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.

### 2026-08-01 (score 71, +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.

### 2026-07-31 (score 70, +4)

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

### 2026-07-30 (score 66, +1)

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

### 2026-07-29 (score 65, +1)

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

### 2026-07-27 (score 64, +1)

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

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (11)

### `suggest_portlandmaps_address` (~371 tokens)

Suggest PortlandMaps Address

1:1 wrapper for /api/suggest/. Search PortlandMaps autocomplete for addresses, intersections, landmarks, or IDs. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

Input parameters:

- `ags`
- `altCoords`: Maps to alt_coords.
- `altIds`: Maps to alt_ids.
- `cache`
- `centerline`
- `city` (string)
- `count` (integer)
- `county` (string)
- `elements`
- `exact`
- `extraParams` (object)
- `geometry`
- `idMatches`: Maps to id_matches.
- `intersections`
- `jurisdiction` (string)
- `landmarks`
- `page` (integer)
- `query` (string, required): Search term. Can be an address, intersection, landmark name, or ID.
- `status` (string)
- `unit` (string)
- `units`

### `get_portlandmaps_detail` (~317 tokens)

Get PortlandMaps Detail

1:1 wrapper for /api/detail/. Fetch a detail record by detail_type, detail_id, and sections. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

Input parameters:

- `cacheClear`: Maps to cache_clear.
- `detailId` (string, required): Maps to detail_id.
- `detailType` (string, required): Maps to detail_type.
- `extraParams` (object)
- `fileId` (string): Maps to file_id.
- `fileType` (string): Maps to file_type.
- `geometry`
- `propertyId` (string): Maps to property_id.
- `sections` (string): Use 'list' for available sections, or '*' for all sections.

### `get_assessor_data` (~312 tokens)

Get Assessor Data

1:1 wrapper for /api/assessor/. Search assessor records by address, property IDs, geometry, or assessor filters.

Input parameters:

- `address` (string)
- `altAccountNumber` (string): Maps to alt_account_number.
- `builtAfter` (integer): Maps to built_after.
- `builtBefore` (integer): Maps to built_before.
- `cache`
- `city` (string)
- `count` (integer)
- `county` (string)
- `download`
- `extraParams` (object)
- `geometry`
- `legalDescription` (string): Maps to legal_description.
- `marketLarger` (number): Maps to market_larger.
- `marketSmaller` (number): Maps to market_smaller.
- `page` (integer)
- `parentStateId` (string): Maps to parent_state_id.
- `primary`
- `propertyId` (string): Maps to property_id.
- `soldAfter` (string): Maps to sold_after, mm/dd/yyyy.
- `soldBefore` (string): Maps to sold_before, mm/dd/yyyy.
- `sortField` (string): Maps to sort_field.
- `sortOrder` (string): Maps to sort_order.
- `sqftLarger` (number): Maps to sqft_larger.
- `sqftSmaller` (number): Maps to sqft_smaller.
- `stateId` (string): Maps to state_id.
- `zipCode` (string): Maps to zip_code.

### `get_permit_data` (~434 tokens)

Get Permit Data

1:1 wrapper for /api/permit/. Search building/trade/enforcement permit records. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

Input parameters:

- `address` (string)
- `applicationNumber` (string): Maps to application_number.
- `businessAssociation` (string): Maps to business_association.
- `cache`
- `ccbNumber` (string): Maps to ccb_number.
- `count` (integer)
- `county` (string)
- `dateFrom` (string): Maps to date_from, mm/dd/yyyy.
- `dateTo` (string): Maps to date_to, mm/dd/yyyy.
- `dateType` (string): Maps to date_type.
- `download`
- `extraParams` (object)
- `ivrNumber` (integer): Maps to ivr_number.
- `neighborhood` (string)
- `neighborhoodDistrict` (string): Maps to neighborhood_district.
- `page` (integer)
- `propertyId` (string): Maps to property_id.
- `searchTypeId` (integer): Maps to search_type_id.
- `sortField` (string): Maps to sort_field.
- `sortOrder` (string): Maps to sort_order.
- `stateId` (string): Maps to state_id.

### `search_landuse_cases` (~427 tokens)

Search Land Use Cases

1:1 wrapper for /api/landuse/. Search land use review cases, including Historic Resource Review and Tree Review. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

Input parameters:

- `applicationNumber` (string): Maps to application_number.
- `businessAssociation` (string): Maps to business_association.
- `cache`
- `conservationDistrict` (string): Maps to conservation_district.
- `count` (integer)
- `dateFrom` (string): Maps to date_from, mm/dd/yyyy.
- `dateTo` (string): Maps to date_to, mm/dd/yyyy.
- `download`
- `extraParams` (object)
- `historicDistrict` (string): Maps to historic_district.
- `ivrNumber` (integer): Maps to ivr_number.
- `milestoneStatus` (string): Maps to milestone_status.
- `neighborhood` (string)
- `neighborhoodDistrict` (string): Maps to neighborhood_district.
- `page` (integer)
- `planDistrict` (string): Maps to plan_district.
- `searchTypeId` (integer): Maps to search_type_id.
- `sortField` (string): Maps to sort_field.
- `sortOrder` (string): Maps to sort_order.

### `search_sewer_records` (~288 tokens)

Search Sewer Records

1:1 wrapper for /api/sewer/. Search sewer assets, as-builts, and easements.

Input parameters:

- `book` (string)
- `comments` (string)
- `compkey` (string)
- `count` (integer)
- `date` (string)
- `download`
- `extraParams` (object)
- `jobName` (string): Maps to job_name.
- `jobNumber` (string): Maps to job_number.
- `location` (string)
- `ordinanceNumber` (string): Maps to ordinance_number.
- `page` (string): Sewer easement page field.
- `pageNum` (integer): Pagination page; maps to page.
- `quarterSection` (string): Maps to quarter_section.
- `quitClaim` (string): Maps to quit_claim.
- `rightOfWay` (string): Maps to right_of_way.
- `serviceRequestNumber` (string): Maps to service_request_number.
- `sortField` (string): Maps to sort_field.
- `sortOrder` (string): Maps to sort_order.
- `trackingNumber` (string): Maps to tracking_number.
- `tvInspectionNumber` (string): Maps to tv_inspection_number.
- `type` (string, required)
- `unitId` (string): Maps to unit_id.
- `workOrderNumber` (string): Maps to work_order_number.

### `query_intersects` (~88 tokens)

Query Intersects

1:1 wrapper for /api/intersects/. Spatial intersection against named city layers such as row, taxlot, describe, street, and waterbody.

Input parameters:

- `buffer` (number)
- `detail` (boolean)
- `geometry` (object, required): ESRI JSON geometry in wkid 2913, 3857, or 4326.
- `include` (array)

### `convert_geometry` (~82 tokens)

Convert Geometry

1:1 wrapper for /api/geometry/. Convert geometry between ESRI, WKT, GeoJSON, GPolyline, and EncodedGPolyline.

Input parameters:

- `from` (string, required)
- `geometry` (string, required): Source geometry as a string. JSON inputs should be JSON.stringify'd.
- `srid` (string)
- `to` (string, required)

### `lookup_agol` (~53 tokens)

Lookup ArcGIS Online Metadata

1:1 wrapper for /api/agol/. Retrieve City of Portland ArcGIS Online metadata, webmaps, locators, and portal info.

Input parameters:

- `id` (string)
- `type` (string, required)

### `list_detail_types` (~27 tokens)

List Detail Types

Return the detail_type values accepted by get_portlandmaps_detail and the identifier each expects.

### `render_parcel_shape` (~281 tokens)

Render Parcel Shape

Render a property's lot as an interactive UI component (inline SVG): a City of Portland aerial photo underlay (showing the true roofline) with the parcel outline, the building footprint(s) on the lot, approximate setback dimensions, a north arrow, and faint neighbouring parcels overlaid on top. Provide a detailType+detailId to fetch geometry, or pass rings directly. Aerial, footprints, and neighbours come from Portland's public ArcGIS layers; set basemap="none" to drop the photo and includeContext=false for just the bare outline. Renders in MCP Apps hosts (Claude) and legacy mcp-ui hosts.

Input parameters:

- `basemap` (string): Aerial photo underlay (true rooflines). 'aerial' fetches a City of Portland image; 'none' renders dark vectors only.
- `detailId` (string): detail_id used to fetch geometry when rings are not supplied.
- `detailType` (string): detail_type used to fetch geometry when rings are not supplied.
- `includeContext` (boolean): Overlay building footprints, setbacks, and neighbouring parcels. Set false for just the lot outline.
- `rings` (array): Web Mercator (EPSG:3857) parcel rings, e.g. geometry.rings. Bypasses fetching.
- `title` (string): Caption shown on the component.

Output parameters:

- `areaSqFt` (number)
- `basemap`
- `buildings` (array)
- `neighbors` (array)
- `rings` (array)
- `setbacks`
- `title` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/mcp-v2#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 71
- 2026-08-01: 71
- 2026-07-31: 70
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://portlandmaps-mcp.vercel.app/mcp/v2
- Changelog RSS feed: https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/mcp-v2/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/mcp-v2/changelog.json
- HTML version of this page: https://verifymcp.io/servers/gptnowllc-portlandmaps-mcp/mcp-v2