MCP.Market

Overture Places MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/overture-places·v0.2.1

Overture Maps places — business and point-of-interest locations (name, category, confidence…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Overture Places yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Overture Places tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Overture Places compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
172 ms
faster than 69% of 30,031 servers

Release history: 3 versions in the registry since 2026-10-10, latest 2026-11-04, typically one every 19 days.

Install Overture Places in Claude Code, Cursor or VS Code

claude mcp add --transport http overture-places https://gateway.pipeworx.io/overture-places/mcp
Add to Cursor

What the publisher says

From the Overture Places repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/overture-places

Business and point-of-interest locations in the United States and the United Kingdom, from the Overture Maps Foundation places theme. Each place carries a name, category, existence confidence score, street address, websites, phones, emails, social links, brand and contributing source record ids. Use it to find places near a point or in a city, to map every location of a company by its website domain, and to count what is in an area.

Part of Pipeworx — an MCP gateway connecting AI agents to 1764+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

businesses matching a name and/or category. Results are ranked by match quality and then by distance (for near) or confidence. Example: the Starbucks branches within 3 km of downtown Austin.

  • placessearch(name?, category?, near{lat,lon} + radiusm | bbox | city + country [+ region], minconfidence?, includeclosed?, limit?):

every location whose website is on a company's domain, which gives that company's physical footprint. Subdomains and paths fold to the registrable domain (https://www.starbucks.com/store-locator → starbucks.com). Returns the total plus counts by country and by state/region.

  • placesbydomain(domain, country?, region?, minconfidence?, includeclosed?, limit?):

the count of places in an area, a breakdown by category, and the highest-confidence places.

  • placesinarea(near + radiusm | bbox | city + country, category?, minconfidence?, include_closed?, limit?):

Every response starts with attribution, a source block (licence, release, terms URL) and dataasof, which is the Overture release the answer came from (for example 2026-09-23.1).

Confidence

Overture gives every place an existence confidence from 0 to 1 and calls it "the primary tool for filtering potential junk data". By default this pack hides places below 0.7, and places marked permanentlyclosed. In the measured sample the distribution breaks sharply at 0.7, and the rows below it were mostly junk. The default keeps about 68% of places. Every place shows its confidence, and every response states the threshold it applied and how many places it hid (hiddenbyfilters). To see everything, pass minconfidence: 0 and include_closed: true.

Coverage and limits

found:false, reason:"outside_coverage" and lists the covered countries.

  • Countries: US and GB. An area or city outside them returns

first. That is about 250,000 places. For a larger area (a whole metro searched by name), the response sets complete:false and explains in coveragewarning what was not searched. placesinarea still gives exact or bounded totals from its index. Narrow the area with near + radiusm for a complete answer.

  • One call scans at most 64 data blocks, nearest the centre of the area

region field is consistent in the US (state codes; full state names are accepted too) but inconsistent in the UK, so leave region out for UK cities. A name that matches several places (several Springfields) uses the largest and lists the others in otherplaceswiththisname.

  • City lookup resolves a locality name from the addresses in the data. The

builders and listing sites (instagram.com, linktr.ee, wixsite.com, yelp.com and similar) identify no single company. placesbydomain refuses them with reason:"platform_domain".

  • Platform domains are not indexed. Social profiles, link pages, site

are indexed. The response always gives the true total in locationslistingdomain and says when the cap applied.

  • Very large domains: the 5,000 highest-confidence locations per domain

rate, and low property completeness". Confidence filtering helps with junk but does not remove duplicates.

  • Overture warns that the theme "is known to contain duplicates, a high junk

Auth

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Overture Places: common questions

Is Overture Places MCP server safe?
Mostly: it is graded B (77/100). Read the Overture Places safety report
How do I install Overture Places?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Overture Places need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Overture Places maintained?
The last commit was 25 days ago (2026-10-10). The latest release is v0.2.1.
Is Overture Places up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Overture Places compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 172 ms (faster than 69% of 30,031 servers). Full comparison.

More from pipeworx-io →