# gmaps.dev (remote · api.gmaps.dev)

Find businesses by what they are and where they are, collect a whole city, and export the list.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `api.gmaps.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-gmaps-gmaps/api.md), [page](https://verifymcp.io/servers/dev-gmaps-gmaps/api)

## Channel facts

- Endpoint: `https://api.gmaps.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-22.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_collection).
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2810 tokens (~156/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 19 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 gmaps.dev MCP server?

gmaps.dev is a hosted endpoint at https://api.gmaps.dev/mcp, 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.

### Claude

```bash
claude mcp add --transport http dev-gmaps-gmaps 'https://api.gmaps.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-gmaps-gmaps": {
      "url": "https://api.gmaps.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-gmaps-gmaps": {
      "type": "http",
      "url": "https://api.gmaps.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-gmaps-gmaps]
url = "https://api.gmaps.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-gmaps-gmaps": {
      "type": "remote",
      "url": "https://api.gmaps.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-gmaps-gmaps --url 'https://api.gmaps.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-gmaps-gmaps:
    url: "https://api.gmaps.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-gmaps-gmaps": {
      "Transport": "http",
      "Url": "https://api.gmaps.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-gmaps-gmaps -t streamable-http -u 'https://api.gmaps.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-gmaps-gmaps": {
      "type": "http",
      "url": "https://api.gmaps.dev/mcp"
    }
  }
}
```

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-10-21 (score 67, +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-20 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-19 (score 66)

First indexed and scored.

## MCP tools (18)

### `get_attributions` (~33 tokens)

List the open-source projects we build on

List the projects credited by gmaps.dev, with their licenses and notices. No API key needed. Costs no credits.

### `search_places` (~302 tokens)

Search for places

Find places by what they are and where they are, such as bakeries in Curitiba. Places we saved from earlier searches come back at once, for free. If they do not fill `limit`, a collection starts to find the rest and the answer includes it: each new place costs one credit as it arrives, and it stops at `limit`, so a search never costs more than `limit` credits. Search again later, or read the collection, to get the new ones; with `wait`, the answer waits up to 60 seconds for them. Needs an API key.

Input parameters:

- `geo` (required): Where to search. Give exactly one of: a Brazilian city as location, a lat/lng point with radiusM, a bbox, or a cityIbge with radiusKm.
- `keywords` (array, required): What to search for, such as ["bakery"]. One search per term.
- `lang` (string): The language to search in. New places come back in it. Two letters, such as pt or en.
- `limit` (integer): How many places you want, from 1 to 120. Also the most a search can cost.
- `minRating`: Keep only places rated at least this, from 1 to 5. Null keeps every place.
- `wait` (integer): Seconds to wait for new places when we have to collect them, up to 60. 0 answers at once with what we already have.

### `get_place` (~93 tokens)

Look up a place

Read one saved place, by our id, Google's cid, Google's place ID, or a Google Maps link to it. It never searches: a place we have not saved answers 404, and searching its area with search_places brings it in. Needs an API key. Costs no credits.

Input parameters:

- `place` (string, required): Our id for the place, Google's cid, Google's place ID, or a Google Maps link to it.

### `create_collection` (~259 tokens)

Start a collection

Search a whole area, square by square, and collect up to maxPlaces of the places in it. Answers straight away with the collection, then works through the area in the background. Read the collection again to see how far it has got. Starting one costs nothing: each new place costs one credit as it arrives, and saved places cost nothing. Needs an API key.

Input parameters:

- `enrich` (array): Add ["emails"] to also look for email addresses. Costs one more credit for each place that has one, and needs a paid plan.
- `geo` (required): Where to search. Give exactly one of: a Brazilian city as location, a lat/lng point with radiusM, a bbox, or a cityIbge with radiusKm.
- `keywords` (array, required): What to search for, such as ["bakery", "coffee shop"]. One search per term.
- `lang` (string): The language to search in. New places come back in it. Two letters, such as pt or en.
- `maxPlaces` (integer): Stop after this many places. Defaults to the most your plan collects at once.
- `minRating`: Keep only places rated at least this, from 1 to 5. Null keeps every place.

### `list_collections` (~100 tokens)

List your collections

Your collections, newest first, with the total so you know how many more there are. Filter by status to find the ones still running. Needs an API key. Costs no credits.

Input parameters:

- `limit` (integer): How many collections to return, from 1 to 100.
- `offset` (integer): How many collections to skip, for reading the next page.
- `status` (string): Show only collections with this status, such as running.

### `get_collection` (~73 tokens)

Read a collection

See where a collection has got to: how much of the area is searched, how many places have arrived, and what it has cost so far. Read it again whenever you want an update. Needs an API key. Costs no credits.

Input parameters:

- `id` (string, required): The collection's id, as create_collection returned it.

### `cancel_collection` (~91 tokens)

Cancel a collection

Stop a collection you no longer want. One that has not started yet stops at once and costs nothing. One already running keeps the places that have arrived and the credits they cost; the search in flight finishes, and nothing new starts. A collection that has already ended cannot be cancelled. Needs an API key. Costs no credits.

Input parameters:

- `id` (string, required): The collection's id, as create_collection returned it.

### `quote_collection` (~246 tokens)

Quote a collection

See what collecting an area would cost before you start it: how much of it we have searched recently, how many places we have saved there (those cost nothing), how many searches are left to run, and the most it can cost in credits. Needs an API key. Costs no credits and starts nothing.

Input parameters:

- `enrich` (array): Add ["emails"] to also look for email addresses. Costs one more credit for each place that has one, and needs a paid plan.
- `geo` (required): Where to search. Give exactly one of: a Brazilian city as location, a lat/lng point with radiusM, a bbox, or a cityIbge with radiusKm.
- `keywords` (array, required): What to search for, such as ["bakery", "coffee shop"]. One search per term.
- `lang` (string): The language to search in. New places come back in it. Two letters, such as pt or en.
- `maxPlaces` (integer): Stop after this many places. Defaults to the most your plan collects at once.
- `minRating`: Keep only places rated at least this, from 1 to 5. Null keeps every place.

### `create_export` (~160 tokens)

Export a collection

Get a link to a collection's places as one file: csv, json or xlsx. The file has the places the collection holds now, even if it is still running. The link opens without an API key for 24 hours, so share it only with people who should see the file. Needs an API key. Costs no credits.

Input parameters:

- `collectionId` (string, required): The collection to export, as create_collection or search_places returned it.
- `format` (string): The file type: csv, json or xlsx. An xlsx file holds up to 50,000 places.
- `locale` (string): The language of the column names in csv and xlsx files: en or pt-BR. Defaults to your account's language.

### `get_export` (~78 tokens)

Read an export

Read an export you made, with its download link, while the link still works. After 24 hours, or once the collection's places are deleted, it answers 404: make a new export from the collection. Needs an API key. Costs no credits.

Input parameters:

- `id` (string, required): The export's id, as create_export returned it.

### `get_coverage` (~163 tokens)

Check an area's coverage

See how much of an area we have already searched for a term, when we last searched it, and how many places we have saved there. Use it to decide whether to collect again or just read the saved places. Needs an API key. Costs no credits and starts nothing.

Input parameters:

- `geo` (required): The area. Give exactly one of: a Brazilian city as location, a lat/lng point with radiusM, a bbox, or a cityIbge with radiusKm.
- `keywords` (array, required): What you would search for, such as ["bakery"]. Coverage is per term: we may have searched an area for one and never for another.
- `lang` (string): The language the search would run in. Two letters, such as pt or en.

### `get_usage` (~49 tokens)

Get credit usage

See this month's credits: what your plan includes, what you have used, what is left today and this month, and the same totals for each API key. Needs an API key. Costs no credits.

### `create_webhook` (~188 tokens)

Add a webhook endpoint

Tell us where to POST when a collection ends, instead of asking us every few seconds whether it is done. The answer shows the signing secret once and never again. Store it, then check every request against it. The body carries counts and a link to the places, never the places themselves. Needs an API key and a paid plan. Costs no credits.

Input parameters:

- `description` (string): Your own note about this endpoint, such as which of your services it is.
- `events` (array): Which events to send here. "collection.completed" fires when a collection ends, even one that found no places; "collection.failed" fires when an error stops it. A collection you cancel sends neither.
- `url` (string, required): Where to POST the event. Must start with https:// and resolve to a public address. We will not send your results unencrypted or into a private network.

### `list_webhooks` (~58 tokens)

List your webhook endpoints

Every endpoint you have added, newest first, with whether it is still receiving events and why we stopped if it is not. Secrets are not shown again after the endpoint is created. Needs an API key and a paid plan. Costs no credits.

### `update_webhook` (~175 tokens)

Change a webhook endpoint

Change which events an endpoint receives, rename it, or switch it off and on. This is how an endpoint comes back after we stopped sending to it: fix your server, then set enabled to true. The failure count starts again from zero. Whatever you leave out stays as it was. Needs an API key and a paid plan. Costs no credits.

Input parameters:

- `description`
- `enabled` (boolean): False to stop sending here without deleting it. True to start again after we switched it off.
- `events` (array): Which events to send here. "collection.completed" fires when a collection ends, even one that found no places; "collection.failed" fires when an error stops it. A collection you cancel sends neither.
- `id` (string, required): The endpoint's id, as create_webhook returned it.

### `delete_webhook` (~89 tokens)

Delete a webhook endpoint

Stop sending to an endpoint and forget it, along with the record of what we sent there. To pause one instead, set enabled to false. That keeps the secret, so you do not have to change your code to turn it back on. Needs an API key and a paid plan. Costs no credits.

Input parameters:

- `id` (string, required): The endpoint's id, as create_webhook returned it.

### `test_webhook` (~116 tokens)

Send a test event

Send a "ping" to one of your endpoints now, so you can check your code reads it and the signature checks out before a real collection depends on it. Answers straight away with the delivery; read the deliveries list a moment later to see what your server said. Needs an API key and a paid plan. Costs no credits.

Input parameters:

- `id` (string, required): The endpoint's id, as create_webhook returned it.
- `message` (string): What the test event should say, so you can spot it in your logs.

### `list_webhook_deliveries` (~113 tokens)

List an endpoint's deliveries

What we sent to one endpoint, newest first: which event, whether it arrived, how many tries it took, and what your server answered. This is where to look when an event never showed up. Kept for 7 days. Needs an API key and a paid plan. Costs no credits.

Input parameters:

- `id` (string, required): The endpoint's id, as create_webhook returned it.
- `limit` (integer): How many deliveries to return, newest first, from 1 to 100.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-gmaps-gmaps/api#diagnostics

## Score history

- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 66
- 2026-10-19: 66

## Common questions

### What is the gmaps.dev MCP server?

gmaps.dev is an MCP server listed in the public MCP registry as dev.gmaps/gmaps. Find businesses by what they are and where they are, collect a whole city, and export the list. This page covers its hosted endpoint (https://api.gmaps.dev/mcp).

### Is the gmaps.dev MCP server safe to use?

gmaps.dev scores 67 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 gmaps.dev MCP server expose?

gmaps.dev exposes 18 tools: get_attributions, search_places, get_place, create_collection, list_collections, and 13 more. Their descriptions and schemas cost roughly 2,386 tokens of context every time the server is loaded.

### Does the gmaps.dev MCP server require authentication?

No. We connected to gmaps.dev without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the gmaps.dev MCP server still maintained?

gmaps.dev is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.gmaps.dev/mcp
- Website: https://gmaps.dev/docs/en/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-gmaps-gmaps/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-gmaps-gmaps/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-gmaps-gmaps/api