Skip to content
External endpointresponds

PortlandMaps (Unofficial)

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

Endpoint URL
https://portlandmaps-mcp.vercel.app/mcp/v2
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
217 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.GPTNowLLC/portlandmaps-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
portlandmaps-mcp-v2
Version
0.2.5
Capability keys
tools, resources, prompts
Tool names
suggest_portlandmaps_address, get_portlandmaps_detail, get_assessor_data, get_permit_data, search_landuse_cases, search_sewer_records, query_intersects, convert_geometry, lookup_agol, list_detail_types, render_parcel_shape
Instructions excerpt

Unofficial MCP server for PortlandMaps: public property, permit, zoning, land-use, sewer, and parcel data for Portland, Oregon (Multnomah, Clackamas, and Washington counties). Not affiliated with or endorsed by the City of Portland. Most detail lookups are keyed by a Taxlots Property ID, not by address. Start with suggest_portlandmaps_address to turn an address, intersection, landmark, or partial ID into candidates carrying the IDs the other tools need. Then: - get_portlandmaps_detail is the workhorse: pass detailType + detailId for zoning, permits, environmental, hazard, crime, parks, schools, and dozens of other layers. Call list_detail_types first to see every detailType and which identifier it expects. - get_assessor_data, get_permit_data, search_landuse_cases, and search_sewer_records are dedicated search endpoints with rich filters. - query_intersects, convert_geometry, and lookup_agol cover spatial intersection, coordinate/format conversion, and ArcGIS Online metadata. - render

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 107ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 244ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 1,029ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 217ms