Google Maps data for agents

sh.fetcher.google-mapsPublished by google-maps.fetcher.shOfficial publisherv1.0.0Updated Oct 24, 2026

4 Google Maps endpoints. Pay per call in USDC via x402.

VerifiedStreamable HTTPWeb executableLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server that gives an assistant live Google Maps place, review and search data as JSON, paid per call in USDC via x402 or prepaid credits.

What you can do
Search Google Maps places and retrieve a single place's details as live JSON data. Fetch a place's reviews or a single review. Check the remaining credit balance for the API key on the connection. Buy prepaid credits with x402 so later calls skip the per-call payment round trip.
When to use it
Useful when an assistant needs current Google Maps place, search or review data rather than a static dataset, and when per-call USDC payment or prepaid credits are acceptable. Check the balance before a long run of paid requests.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. Paid tools cost $0.005 per call, settled with x402 or an Authorization: Bearer bby_live_... credits key. Top-up requires a minimum of $1 and a paying wallet when no key is supplied. Network access is required.
Before you install
Every data tool costs money per call, and top-up spends at least $1 from a wallet. The connection carries a bearer credits key, and without one the paying wallet becomes the account and a new API key is minted. Review the spending before long automated runs.

Installation

In SourceWeft

  1. Open Google Maps data for agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/sh.fetcher.google-maps%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google-maps-data-for-agents": {
      "type": "http",
      "url": "https://google-maps.fetcher.sh/mcp"
    }
  }
}

Tools

6

google_maps_place

Paid ($0.005). Place — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

ParametersfidrequiredcountryCodelanguageCode

google_maps_place_reviews

Paid ($0.005). Place reviews — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

ParametersfidrequiredsortcursorcountryCodelanguageCode

google_maps_review

Paid ($0.005). Review — Google Maps. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

Parametersidrequired

check_balance

Free. Show the remaining credit balance for the API key sent in this connection's Authorization header. Call this before a long run of paid requests.

Takes no parameters.

topup_credits

Paid (the amount you choose, minimum $1). Buy prepaid credits with x402 so later calls skip the per-call payment round trip. With an Authorization: Bearer bby_live_... header on this connection it recharges that key. Without one, the paying wallet becomes the account and a new API key is minted and returned once — store it as a secret, it cannot be recovered.

Parametersamountrequiredrotate

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.