PortlandMaps (Unofficial)
REMOTE · PORTLANDMAPS-MCP.VERCEL.APP · 2 COMPONENTS · SCANNED SEP 20
Unofficial MCP server for the public PortlandMaps property/permit/zoning API. Not city-affiliated.
Available components
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- 80% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- Structured output schemas are declared (9% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the PortlandMaps (Unofficial) MCP server?
PortlandMaps (Unofficial) is a hosted endpoint at https://portlandmaps-mcp.vercel.app/mcp/v2, 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 · portlandmaps-mcp.vercel.app
claude mcp add --transport http gptnowllc-portlandmaps-mcp 'https://portlandmaps-mcp.vercel.app/mcp/v2'
{
"mcpServers": {
"gptnowllc-portlandmaps-mcp": {
"url": "https://portlandmaps-mcp.vercel.app/mcp/v2"
}
}
} {
"servers": {
"gptnowllc-portlandmaps-mcp": {
"type": "http",
"url": "https://portlandmaps-mcp.vercel.app/mcp/v2"
}
}
} [mcp_servers.gptnowllc-portlandmaps-mcp] url = "https://portlandmaps-mcp.vercel.app/mcp/v2"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gptnowllc-portlandmaps-mcp": {
"type": "remote",
"url": "https://portlandmaps-mcp.vercel.app/mcp/v2",
"enabled": true
}
}
} openclaw mcp add gptnowllc-portlandmaps-mcp --url 'https://portlandmaps-mcp.vercel.app/mcp/v2' --transport streamable-http
mcp_servers:
gptnowllc-portlandmaps-mcp:
url: "https://portlandmaps-mcp.vercel.app/mcp/v2" {
"McpServers": {
"gptnowllc-portlandmaps-mcp": {
"Transport": "http",
"Url": "https://portlandmaps-mcp.vercel.app/mcp/v2"
}
}
} assistant mcp add gptnowllc-portlandmaps-mcp -t streamable-http -u 'https://portlandmaps-mcp.vercel.app/mcp/v2'
{
"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.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://portlandmaps-mcp.vercel.app/mcp/v2
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of portlandmaps-mcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://portlandmaps-mcp.vercel.app/mcp/v2 | Verified | 200 | |
| http (plaintext) | http://portlandmaps-mcp.vercel.app/mcp/v2 | HTTPS enforced | 308 | https://portlandmaps-mcp.vercel.app/mcp/v2 |
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 →
convert_geometry Convert Geometry ~82
1:1 wrapper for /api/geometry/. Convert geometry between ESRI, WKT, GeoJSON, GPolyline, and EncodedGPolyline.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| geometry | string | yes | Source geometry as a string. JSON inputs should be JSON.stringify'd. |
| srid | string | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
get_assessor_data Get Assessor Data ~312
1:1 wrapper for /api/assessor/. Search assessor records by address, property IDs, geometry, or assessor filters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_permit_data Get Permit Data ~434
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_portlandmaps_detail Get PortlandMaps Detail ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cacheClear | – | – | Maps to cache_clear. |
| detailId | string | yes | Maps to detail_id. |
| detailType | string | yes | 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. |
No output schema declared.
No examples provided.
list_detail_types List Detail Types ~27
Return the detail_type values accepted by get_portlandmaps_detail and the identifier each expects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_agol Lookup ArcGIS Online Metadata ~53
1:1 wrapper for /api/agol/. Retrieve City of Portland ArcGIS Online metadata, webmaps, locators, and portal info.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
query_intersects Query Intersects ~88
1:1 wrapper for /api/intersects/. Spatial intersection against named city layers such as row, taxlot, describe, street, and waterbody.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer | number | – | – |
| detail | boolean | – | – |
| geometry | object | yes | ESRI JSON geometry in wkid 2913, 3857, or 4326. |
| include | array | – | – |
No output schema declared.
No examples provided.
render_parcel_shape Render Parcel Shape ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| areaSqFt | number | yes | – |
| basemap | – | – | – |
| buildings | array | – | – |
| neighbors | array | – | – |
| rings | array | yes | – |
| setbacks | – | – | – |
| title | string | – | – |
No examples provided.
search_landuse_cases Search Land Use Cases ~427
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_sewer_records Search Sewer Records ~288
1:1 wrapper for /api/sewer/. Search sewer assets, as-builts, and easements.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| unitId | string | – | Maps to unit_id. |
| workOrderNumber | string | – | Maps to work_order_number. |
No output schema declared.
No examples provided.
suggest_portlandmaps_address Suggest PortlandMaps Address ~371
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Search term. Can be an address, intersection, landmark name, or ID. |
| status | string | – | – |
| unit | string | – | – |
| units | – | – | – |
No output schema declared.
No examples provided.
What is the PortlandMaps (Unofficial) MCP server?
PortlandMaps (Unofficial) is an MCP server listed in the public MCP registry as io.github.GPTNowLLC/portlandmaps-mcp. Unofficial MCP server for the public PortlandMaps property/permit/zoning API. Not city-affiliated. This page covers its hosted endpoint (https://portlandmaps-mcp.vercel.app/mcp/v2).
Is the PortlandMaps (Unofficial) MCP server safe to use?
PortlandMaps (Unofficial) scores 83 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 PortlandMaps (Unofficial) MCP server expose?
PortlandMaps (Unofficial) exposes 11 tools: suggest_portlandmaps_address, get_portlandmaps_detail, get_assessor_data, get_permit_data, search_landuse_cases, and 6 more. Their descriptions and schemas cost roughly 2,680 tokens of context every time the server is loaded.
Does the PortlandMaps (Unofficial) MCP server require authentication?
No. We connected to PortlandMaps (Unofficial) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PortlandMaps (Unofficial) MCP server still maintained?
PortlandMaps (Unofficial) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.