Is the Latlng MCP server down?

mcp-registry/work.latlng.mcp/latlng · v0.1.0

As of 2026-10-26 23:41 UTC, the Latlng MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Geocoding, reverse geocoding, and places search for LatLng.

Point your MCP client at this streamable-http endpoint: https://mcp.latlng.work/mcp

Agent-readiness: C (72/100)

What to fix (3)

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fwork.latlng.mcp%2Flatlng/fixes

{
  "name": "find_nearby_places",
  "description": "Find points of interest near a latitude and longitude.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "geocode_address",
  "description": "Convert an address or place name into latitude and longitude coordinates.",
  "inputSchema": {
    "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
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "list_place_categories",
  "description": "List supported place categories for place search and nearby queries.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/work.latlng.mcp/latlng"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/work.latlng.mcp/latlng"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~684 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• search_places ~188 tokens
• geocode_address ~163 tokens
• find_nearby_places ~154 tokens
• reverse_geocode ~125 tokens
• list_place_categories ~54 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fwork.latlng.mcp%2Flatlng.svg)](https://glimind.com/server/mcp-registry%2Fwork.latlng.mcp%2Flatlng?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fwork.latlng.mcp%2Flatlng?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fwork.latlng.mcp%2Flatlng.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fwork.latlng.mcp%2Flatlng.svg
   :target: https://glimind.com/server/mcp-registry%2Fwork.latlng.mcp%2Flatlng?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f0fa482d114dee04…, first seen 2026-10-17, included at leaf 14111 of 76,148. Version history · verify what your client received.

Tools (5)

• find_nearby_places
• geocode_address
• list_place_categories
• reverse_geocode
• search_places

Compare: most reliable search servers · most reliable data servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Latlng MCP server down right now?

As of 2026-10-26 23:41 UTC, the Latlng MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Latlng MCP server provide?

Latlng MCP server advertises 5 tools, including find_nearby_places, geocode_address, list_place_categories, reverse_geocode, search_places.

How do I install Latlng MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.latlng.work/mcp

Is the Latlng MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Latlng MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.