# Overture Places (npm · @pipeworx/mcp-overture-places) Overture Maps places — business and point-of-interest locations (name, category, confidence… - Trust score: 81/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`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-overture-places/overture-places-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-overture-places/overture-places-mcp) - npm · `@pipeworx/mcp-overture-places`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places.md), [page](https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-overture-places` - 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-overture-places). - Clear OSI-approved license (MIT). - Actively maintained (last published 1 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 57/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 1085 tokens (~361/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 Overture Places MCP server? Overture Places runs locally as an npm package, launched with npx -y @pipeworx/mcp-overture-places. 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-overture-places -- npx -y @pipeworx/mcp-overture-places ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-overture-places": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-overture-places" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-overture-places": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-overture-places" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-overture-places -- npx -y @pipeworx/mcp-overture-places ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-overture-places": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-overture-places" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-overture-places --command npx --arg -y --arg @pipeworx/mcp-overture-places ``` ### Hermes ```yaml mcp_servers: pipeworx-io-overture-places: command: "npx" args: ["-y", "@pipeworx/mcp-overture-places"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-overture-places": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-overture-places" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-overture-places -t stdio -c npx -a -y @pipeworx/mcp-overture-places ``` ### Other ```json { "mcpServers": { "pipeworx-io-overture-places": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-overture-places" ] } } } ``` ## 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 81, +16) - [security improvement] Malware scan: unverified → pass ### 2026-11-04 (score 65, −15) - [security regression] Malware scan: pass → unverified - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-11-03 (score 80, +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-10-31 (score 79, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 78) First indexed and scored. ## MCP tools (3) ### `places_search` (~405 tokens) Find businesses and points of interest by name and/or category near a point, inside a bbox, or within a city, in the United States and the United Kingdom (Overture Maps places). Returns each place with name, category, confidence score, street address, websites, phones, emails, social links, brand and source record ids, nearest or best match first. Answers "where is the nearest Starbucks to these coordinates", "find dentists in Austin TX", "list Pret A Manger shops in London". Input parameters: - `bbox` (array): Bounding box [west, south, east, north] in decimal degrees, as an alternative to near. - `category` (string): Overture category, e.g. "coffee_shop", "dentist", "hotel", "restaurant", "pharmacy". Matches the basic category, the taxonomy primary or any level of its hierarchy. - `city` (string): City / town / locality name, e.g. "Austin" or "London". Needs country. - `country` (string): Country for city: "US" or "GB" (also accepts "UK", "United States", "United Kingdom"). - `include_closed` (boolean): Include places Overture marks permanently_closed. Default false. - `limit` (number): Max places returned (1–200, default 25). - `min_confidence` (number): Hide places whose Overture existence confidence is below this (0–1). Default 0.7. - `name` (string): Business name or words in it, e.g. "Starbucks" or "Pret A Manger". Optional when category is given. - `near` (object): Centre point {lat, lon} in decimal degrees. Use with radius_m. - `radius_m` (number): Search radius in metres around near (50–50000). - `region` (string): Optional state or region to disambiguate city, e.g. "TX" or "Texas". ### `places_by_domain` (~253 tokens) List every physical location whose website is on a company domain — the store / office / branch footprint of a business — in the United States and the United Kingdom (Overture Maps places). Give a domain like "starbucks.com" or a full URL; subdomains and paths fold to the registrable domain. Returns the total count, counts by country and by state/region, and the locations with addresses, phones and confidence. Answers "how many locations does acme.com have and where". Input parameters: - `country` (string): Optional: only locations in this country ("US" or "GB"). - `domain` (string, required): Company domain or website URL, e.g. "starbucks.com", "https://www.tesco.com/stores". - `include_closed` (boolean): Include places Overture marks permanently_closed. Default false. - `limit` (number): Max locations returned (1–1000, default 100). Counts always cover all matches. - `min_confidence` (number): Hide places whose Overture existence confidence is below this (0–1). Default 0.7. - `region` (string): Optional: only locations in this state/region, e.g. "TX". ### `places_in_area` (~371 tokens) Count and list the businesses and points of interest inside an area — a bbox, a radius around a point, or a whole city — in the United States and the United Kingdom (Overture Maps places), optionally for one category. Returns the total, a breakdown by category, and the highest-confidence places. Answers "how many restaurants are in this bbox", "what kinds of businesses are within 500 m of this address", "how many gyms are in Manchester". Input parameters: - `bbox` (array): Bounding box [west, south, east, north] in decimal degrees, as an alternative to near. - `category` (string): Overture category, e.g. "coffee_shop", "dentist", "hotel", "restaurant", "pharmacy". Matches the basic category, the taxonomy primary or any level of its hierarchy. - `city` (string): City / town / locality name, e.g. "Austin" or "London". Needs country. - `country` (string): Country for city: "US" or "GB" (also accepts "UK", "United States", "United Kingdom"). - `include_closed` (boolean): Include places Overture marks permanently_closed. Default false. - `limit` (number): Max places listed (0–200, default 25). Counts cover the whole area. - `min_confidence` (number): Hide places whose Overture existence confidence is below this (0–1). Default 0.7. - `near` (object): Centre point {lat, lon} in decimal degrees. Use with radius_m. - `radius_m` (number): Search radius in metres around near (50–50000). - `region` (string): Optional state or region to disambiguate city, e.g. "TX" or "Texas". ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places#diagnostics ## Score history - 2026-11-05: 81 - 2026-11-04: 65 - 2026-11-03: 80 - 2026-11-02: 79 - 2026-11-01: 79 - 2026-10-31: 79 - 2026-10-30: 78 - 2026-10-29: 78 ## Common questions ### What is the Overture Places MCP server? Overture Places is an MCP server listed in the public MCP registry as io.github.pipeworx-io/overture-places. Overture Maps places, business and point-of-interest locations (name, category, confidence… This page covers its npm package (@pipeworx/mcp-overture-places). ### Is the Overture Places MCP server safe to use? Overture Places scores 81 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 Overture Places MCP server expose? Overture Places exposes 3 tools: places_search, places_by_domain, places_in_area. Their descriptions and schemas cost roughly 1,029 tokens of context every time the server is loaded. ### Is the Overture Places MCP server still maintained? Overture Places 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 Overture Places MCP server under? Overture Places declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ### What did VerifyMCP test on the Overture Places MCP server? VerifyMCP ran 16 checks on Overture Places, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-overture-places - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-overture-places - Repository: https://github.com/pipeworx-io/mcp-overture-places - Website: https://pipeworx.io/packs/overture-places - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-overture-places/pipeworx-mcp-overture-places