_ registry / mcp streamable-http · checked 5h ago

wheremind

https://wheremind.ai

Registry code: 5f546d88053ad608

api record

Wheremind is location for your AI. Live place search, place details, nearby search, geocoding, and turn-by-turn directions. Use it whenever the user needs a real place, address, or route. Do not invent locations. Pick the tool that matches the ask: places_search_text to find places by name, category, or "X near Y"; places_nearby for places around coordinates you already have; places_details for one place's phone, website, hours, or rating by place_id; geocode to turn an address into coordinates or coordinates into an address; directions for a route, distance, or travel time from A to B. Show…

endpoint
https://wheremind.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is wheremind live?
Yes — it answered the hub's last check (checked 5h ago). It answered 99% of checks over the last 30 days.
Is wheremind free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does wheremind have?
5 tools: geocode, directions, places_details, places_nearby, places_search_text.
Is wheremind safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.7%· all time 99.7%

latency
444ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 329 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· HTTP 500
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search places
  • geocode addresses
  • get turn-by-turn routes
takes → gives
text → data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 auth-required 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • geocode auth-required 23h ago

    Convert an address to lat/lng (forward: pass address), or lat/lng to an address (reverse: pass latitude and longitude). Use when the user needs coordinates or a normalized address, or before places_nearby. To find businesses use places_search_text; directions accepts addresses directly, so geocoding first is not required. Returns formatted address, lat/lng, place_id, types, and plus code.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "address": {
          "type": "string",
          "description": "Address to forward-geocode"
        },
        "latitude": {
          "type": "number",
          "description": "Latitude for reverse geocode"
        },
        "longitude": {
          "type": "number",
          "description": "Longitude for reverse geocode"
        },
        "field_mask": {
          "type": "string"
        },
        "language_code": {
          "type": "string"
        }
      }
    }
    arguments 23 lines
  • directions auth-required 14h ago

    Compute a route from origin to destination by DRIVE, WALK, BICYCLE, TRANSIT, or TWO_WHEELER. Use when the user asks how to get somewhere, how far it is, or how long it takes. Origin and destination may be an address string, "lat,lng", or an object with place_id. Returns total duration and distance, an encoded polyline, and per-leg turn-by-turn steps (maneuver, instruction text, distance, duration, start/end lat/lng).

    mcp-tool

    {
      "type": "object",
      "required": [
        "origin",
        "destination"
      ],
      "properties": {
        "origin": {
          "description": "Address string, 'lat,lng', or {address|place_id|latitude,longitude}"
        },
        "field_mask": {
          "type": "string",
          "description": "Optional Routes X-Goog-FieldMask override. Default includes turn-by-turn navigationInstruction without Pro fields (localizedValues, travelAdvisory)."
        },
        "destination": {
          "description": "Address string, 'lat,lng', or {address|place_id|latitude,longitude}"
        },
        "travel_mode": {
          "type": "string",
          "description": "DRIVE, WALK, BICYCLE, TRANSIT, TWO_WHEELER"
        },
        "alternatives": {
          "type": "boolean"
        },
        "intermediates": {
          "type": "array"
        },
        "language_code": {
          "type": "string"
        }
      }
    }
    arguments 32 lines
  • places_details auth-required 14h ago

    Get details for one known place by place_id (from places_search_text or places_nearby). Use when the user asks for a specific place's phone number, website, opening hours, or rating. Returns name, formatted address, lat/lng, rating, opening hours, phone, website, and attributions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "place_id"
      ],
      "properties": {
        "place_id": {
          "type": "string",
          "description": "Place id, with or without the places/ prefix"
        },
        "field_mask": {
          "type": "string"
        },
        "language_code": {
          "type": "string"
        }
      }
    }
    arguments 18 lines
  • places_nearby auth-required 23h ago

    List places within a radius (meters) of a lat/lng you already have, such as the user's location or a geocode result, optionally filtered by Places types (e.g. ["restaurant"]) and ranked by DISTANCE or POPULARITY. For free-text, name, or city queries use places_search_text instead. Returns place_id, name, formatted address, lat/lng, types, rating, opening hours, and attributions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "latitude",
        "longitude",
        "radius"
      ],
      "properties": {
        "radius": {
          "type": "number",
          "description": "Circle radius in meters"
        },
        "latitude": {
          "type": "number"
        },
        "longitude": {
          "type": "number"
        },
        "field_mask": {
          "type": "string"
        },
        "language_code": {
          "type": "string"
        },
        "included_types": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Places types, e.g. [\"restaurant\"]"
        },
        "rank_preference": {
          "type": "string",
          "description": "DISTANCE or POPULARITY"
        },
        "max_result_count": {
          "type": "integer"
        }
      }
    }
    arguments 40 lines
  • places_search_text auth-required 23h ago

    Find places by free text: a business name, a category, or "X in/near Y" (e.g. "coffee in Porto", "pharmacies near Lisbon Oriente"). Default choice for finding places. Use places_nearby only when you already have exact coordinates. Returns up to 20 places, each with place_id, name, formatted address, lat/lng, types, rating, opening hours (open_now and weekly hours), and attributions. Pass a place_id to places_details for phone or website.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free-text query, e.g. 'coffee in Austin'"
        },
        "radius": {
          "type": "number",
          "description": "Optional location bias radius in meters"
        },
        "latitude": {
          "type": "number",
          "description": "Optional location bias latitude"
        },
        "longitude": {
          "type": "number",
          "description": "Optional location bias longitude"
        },
        "field_mask": {
          "type": "string"
        },
        "included_type": {
          "type": "string",
          "description": "Optional Places type filter"
        },
        "language_code": {
          "type": "string"
        },
        "max_result_count": {
          "type": "integer",
          "description": "1-20"
        }
      }
    }
    arguments 38 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5f546d88053ad608.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5f546d88053ad608/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5f546d88053ad608/badge.svg)](https://brick.blue/agent/5f546d88053ad608?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.