Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LatLng

REMOTE · MCP.LATLNG.WORK · SCANNED SEP 20

Geocoding, reverse geocoding, and places search for LatLng.

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 318 tokens (~63/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the LatLng MCP server?

LatLng is a hosted endpoint at https://mcp.latlng.work/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.

remote · mcp.latlng.work

# add to Claude Code
claude mcp add --transport http work-latlng-mcp-latlng 'https://mcp.latlng.work/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "work-latlng-mcp-latlng": {
      "url": "https://mcp.latlng.work/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "work-latlng-mcp-latlng": {
      "type": "http",
      "url": "https://mcp.latlng.work/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.work-latlng-mcp-latlng]
url = "https://mcp.latlng.work/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "work-latlng-mcp-latlng": {
      "type": "remote",
      "url": "https://mcp.latlng.work/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add work-latlng-mcp-latlng --url 'https://mcp.latlng.work/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  work-latlng-mcp-latlng:
    url: "https://mcp.latlng.work/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "work-latlng-mcp-latlng": {
      "Transport": "http",
      "Url": "https://mcp.latlng.work/mcp"
    }
  }
}
# add to Vellum
assistant mcp add work-latlng-mcp-latlng -t streamable-http -u 'https://mcp.latlng.work/mcp'
// mcp.json
{
  "mcpServers": {
    "work-latlng-mcp-latlng": {
      "type": "http",
      "url": "https://mcp.latlng.work/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://mcp.latlng.work/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=latlng.work CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 968a75444ca8ace913c0b8f67c86c891
SANs: latlng.work, mcp.latlng.work, *.mcp.latlng.work
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.latlng.work. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
work. present 16252 8 Verified
latlng.work. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.latlng.work/mcp Verified 200
http (plaintext) http://mcp.latlng.work/mcp HTTPS enforced 301 https://mcp.latlng.work/mcp
MCP tools · 5 exposed · ~318 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_nearby_places ~69

Find points of interest near a latitude and longitude.

NameTypeReqDescription
latnumberyesCenter latitude.
limitinteger
lonnumberyesCenter longitude.
radiusinteger
typestringOptional place category, for example restaurant or cafe.

No output schema declared.

No examples provided.

geocode_address ~80

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

NameTypeReqDescription
langstringOptional language code, for example en.
latnumberOptional latitude to bias results.
limitinteger
lonnumberOptional longitude to bias results.
querystringyesAddress or place name to geocode.

No output schema declared.

No examples provided.

list_place_categories ~20

List supported place categories for place search and nearby queries.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reverse_geocode ~55

Convert latitude and longitude coordinates into an address.

NameTypeReqDescription
langstringOptional language code, for example en.
latnumberyesLatitude.
limitinteger
lonnumberyesLongitude.

No output schema declared.

No examples provided.

search_places ~94

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

NameTypeReqDescription
countrystringOptional country code, for example US.
latnumberOptional latitude to bias results.
limitinteger
lonnumberOptional longitude to bias results.
querystringyesPlace name or search query.
typestringOptional place category, for example restaurant or cafe.

No output schema declared.

No examples provided.

Common questions

What is the LatLng MCP server?

LatLng is an MCP server listed in the public MCP registry as work.latlng.mcp/latlng. Geocoding, reverse geocoding, and places search for LatLng. This page covers its hosted endpoint (https://mcp.latlng.work/mcp).

Is the LatLng MCP server safe to use?

LatLng scores 77 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 LatLng MCP server expose?

LatLng exposes 5 tools: geocode_address, reverse_geocode, search_places, find_nearby_places, list_place_categories. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.

Does the LatLng MCP server require authentication?

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

Is the LatLng MCP server still maintained?

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