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

latlng-mcp

https://mcp.latlng.work

Registry code: 13d07d1711fc2b63

api record

Geocoding, reverse geocoding, and places search for LatLng.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.latlng.work/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
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 latlng-mcp live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is latlng-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does latlng-mcp have?
5 tools: geocode_address, reverse_geocode, find_nearby_places, search_places, list_place_categories.
Is latlng-mcp 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.6%

90 days 99.7%· all time 99.7%

latency
166ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 380 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
maps travel & places geocoding & maps
used for
  • geocode an address
  • reverse geocode coordinates
  • find places near a location
  • search places by name
takes → gives
text, data → data
tools
5 reads
_ 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
1 open 4 never probed 1 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.

  • list_place_categories reads open 12h ago

    List supported place categories for place search and nearby queries.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • geocode_address reads unknown never probed

    Convert an address or place name into latitude and longitude coordinates.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Optional latitude to bias results."
    },
    "lon": {
      "type": "number",
      "description": "Optional longitude to bias results."
    },
    "lang": {
      "type": "string",
      "description": "Optional language code, for example en."
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 20,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Address or place name to geocode."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • reverse_geocode reads unknown never probed

    Convert latitude and longitude coordinates into an address.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Latitude."
    },
    "lon": {
      "type": "number",
      "description": "Longitude."
    },
    "lang": {
      "type": "string",
      "description": "Optional language code, for example en."
    },
    "limit": {
      "type": "integer",
      "default": 1,
      "maximum": 10,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • find_nearby_places reads unknown 12h ago

    Find points of interest near a latitude and longitude.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Center latitude."
    },
    "lon": {
      "type": "number",
      "description": "Center longitude."
    },
    "type": {
      "type": "string",
      "description": "Optional place category, for example restaurant or cafe."
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1
    },
    "radius": {
      "type": "integer",
      "default": 1000,
      "maximum": 50000,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • search_places reads unknown 12h ago

    Search for places by name, optionally biased by location and category.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "description": "Optional latitude to bias results."
    },
    "lon": {
      "type": "number",
      "description": "Optional longitude to bias results."
    },
    "type": {
      "type": "string",
      "description": "Optional place category, for example restaurant or cafe."
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Place name or search query."
    },
    "country": {
      "type": "string",
      "description": "Optional country code, for example US."
    }
  },
  "additionalProperties": false
}
    arguments 35 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 13d07d1711fc2b63.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/13d07d1711fc2b63/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/13d07d1711fc2b63/badge.svg)](https://brick.blue/agent/13d07d1711fc2b63?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.