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.

LatLong Maps

REMOTE · GEOCP.LATLONG.AI

Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language.

Available components

0 this week 69 Trust /100

Last scanned (19 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 Security51
Transport & Reachability100
Schema Quality & AI Usability50
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6957 tokens (~869/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 7% of tool parameters carry a description.Partial
  • Structured output schemas are declared (38% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • “question_to_map” added an optional parameter “legend_title” cosmetic
    • “question_to_map” added an optional parameter “subtitle” cosmetic
    • “question_to_map” added an optional parameter “title” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 24 Oct 26 +8
    • Stability: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
  • 23 Oct 26 61
    • The server rewrote its instructions, which are the text every model session reads security
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 21 Nov 2026 · Probed https://geocp.latlong.ai/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=latlong.ai CN=Amazon RSA 2048 M01,O=Amazon,C=US 8 Sept 2026 24 Mar 2027 RSA 2048 SHA256-RSA 3b240edaf335e56dbc980737fb6b221
SANs: latlong.ai, *.latlong.ai
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of geocp.latlong.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
latlong.ai. No DS 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://geocp.latlong.ai/mcp/ Verified 200
http (plaintext) http://geocp.latlong.ai/mcp/ Inconclusive 308 /mcp
MCP tools · 8 exposed · ~3,099 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
compute_column ~294

Add a column computed from arithmetic over an uploaded file's numeric columns, then map it. Pass file_key, expression and result_column, e.g. {"file_key": "...", "expression": "(revenue - cost) / population", "result_column": "profit_per_capita"}. Operators: + - * / % and parentheses, or a single comparison (> < >= <= ==) between two operands. Column names are matched case-insensitively and may contain spaces; quote a name that looks like a number with backticks, e.g. `2023` - `2020`. A row whose referenced cells are blank or a missing-data marker (-, NA, N/A), or that divides by zero, gets an empty value. The uploaded file is never changed: the reply carries a NEW file_key holding a copy with the column added. To map it, call question_to_map with that file_key and value_column = result_column. Use this instead of calculating values yourself. If it is refused, tell the user the error; do not calculate the values yourself or upload a rewritten file.

NameTypeReqDescription
expressionstringyesarithmetic over column names, e.g. (revenue - cost) / population; operators + - * / % and parentheses, or one comparison > < >= <= ==
file_keystringyes–
result_columnstring––
sheetstring––

No output schema declared.

No examples provided.

geocode ~313

Geocode addresses from an uploaded CSV or XLSX file into latitude/longitude. Pass a file_key from upload_file. Single place, no file: pass only address (e.g. {"address": "India Gate, New Delhi"}). The reply carries latitude, longitude, address, pincode, city, district, state and landmark. status=not_found means no match; tell the user rather than answering yourself. Column selection: if you know it, pass address_column (or address_columns for several). Otherwise the server asks the geo-match service to detect it. When the answer is not unambiguous — several address columns, a weak match, or only structured columns like District/State/PIN that must be combined — the response is status=clarification_required with candidates and ready-to-fire guidance actions. Present the choice to the user and re-call with their answer; never invent a column name. The result overwrites the same file_key as a new version, plus a small preview, not the full rows. Pass that file_key to question_to_map to map the coordinates, or hand the user file_url (a signed download link, when present) to fetch the file directly.

NameTypeReqDescription
addressstring––
address_columnstring––
address_columnsnull|array––
compose_columnsnull|array––
file_keystring––
force_newboolean––
job_idstring––
sheetstring––

No output schema declared.

No examples provided.

get_capabilities ~55

Return the server's capability matrix: supported map types, geo types, output formats, classification methods, and the list of tools available in this process (which varies by configuration). Call this first to discover what the server can do.

Input schema present but exposes no named parameters.

NameTypeReqDescription
auto_level_detectionbooleanyes–
available_indicesnull|arrayyes–
available_toolsnull|arrayyes–
classification_methodsnull|arrayyes–
default_outputstringyes–
geo_detectionbooleanyes–
geo_levelsnull|arrayyes–
guidancenull|object––
index_modesnull|arrayyes–
map_featuresnull|arrayyes–
map_typesnull|arrayyes–
output_formatsnull|arrayyes–
png_supportedbooleanyes–
stateless_onlybooleanyes–
svg_defaultbooleanyes–

No examples provided.

pincode_lookup ~272

Look up Indian pincodes: city, district and state. One pincode, no file: {"pincode": "560019"} also returns the post offices it covers with their coordinates. status=not_found means the pincode does not exist; tell the user rather than answering yourself. A file (including a local CSV the user names): upload it with upload_file first, then pass file_key (and pincode_column if you know it). Do not look the rows up one by one or write the result file yourself — this tool writes it. Every row gains city, district, state and pincode_status columns; the file is written back over file_key as a new version and file_url is a download link. Show the user the preview and offer the link. Each unique pincode costs one lookup. A clarification_required reply asks which column holds the pincodes. Large files return status=accepted with a job_id: poll {"job_id": "..."} until completed.

NameTypeReqDescription
file_keystring––
force_newboolean––
job_idstring––
pincode––one 6-digit Indian pincode, e.g. "560019" (a number is accepted too)
pincode_columnstring––
sheetstring––

No output schema declared.

No examples provided.

question_to_map ~674

Render a geographic map from your data. Call upload_file first to ingest a CSV/XLSX file, then pass the returned file_key: {"question": "show total by pincode", "file_key": "mcp-uploads/<user-id>/2026/01/15/<uuid>.csv"}. The file_key is reusable — for additional questions on the same file, pass the same file_key again without re-uploading. Alternatively, pass rows directly as 'data' (e.g. from the upload_file preview): {"question": "show total by pincode", "data": [<rows>]} geo_column and value_column are preferred if easily identifiable from the column names, but not required — the server auto-detects them using a geo-match service that matches your data against known Indian geographies (states, districts, ACs, PCs, pincodes, RTOs, cities). Hints: geo_column usually contains place names (state, district, city, pincode, constituency) or numeric codes (pincode=560049); value_column usually contains the metric to plot (sales, count, total, percentage) or a category (party affiliation, status, type). If value_column is 'total' and doesn't exist in data, all numeric columns are summed automatically. String value columns render as categorical maps (each distinct value gets its own color, e.g. party affiliation). If the server cannot determine which columns to use, it returns a 'clarification_required' response with suggested columns and guidance — pick a geo_column and value_column from the suggestions and re-call. Supported geo types: state, district, pincode, rto, city, ac, pc. Points mode: if your file has latitude/longitude columns (e.g. from a prior geocoding step, or coordinates you already had) and your question asks to plot/pin/mark locations ("plot my stores", "show me the outlet locations", "mark these points"), the server detects the coordinate columns automatically and renders markers instead of shaded regions — no geo_column/value_column needed. The boundary lines drawn beneath the markers and how far the map zooms are chosen automatically from where the…

NameTypeReqDescription
datanull|array––
detected_geonull|object––
enrich_withnull|object––
file_keystring––
geo_columnstring––
geo_levelstring––
legend_titlestring––
map_typestring––
output_formatstring––
questionstringyes–
render_paramsobject––
sheetstring––
state_hintnull|array––
styleobject––
subtitlestring––
tablestring––
titlestring––
value_columnstring––
NameTypeReqDescription
aggregation_appliednull|object––
clarificationnull|object––
computed_datanull|object––
confidencenumber––
guidancenull|object––
level_resolutionnull|object––
mapnull|object––
modestringyes–
points_plottedinteger––
points_rejectedinteger––
rejected_rowsnull|array––
resolution_methodstring––
resolved_paramsnull|object––
usagenull|object––
warningsnull|array––

No examples provided.

reverse_geocode ~351

Turn latitude/longitude coordinates in an uploaded CSV or XLSX into addresses. Pass a file_key from upload_file. Single point, no file: pass only latitude and longitude in decimal degrees (e.g. {"latitude": 28.6129, "longitude": 77.2295}). The reply carries address, pincode, city, district, state and landmark. status=not_found means no match; tell the user rather than answering yourself. Column selection: pass latitude_column and longitude_column, or latlong_column for a single combined column, or coordinate_pairs for several sets. Otherwise the server detects them. When the answer is not unambiguous — several coordinate columns, a weak match, coordinates outside the supported region, or coarse whole-number values — the response is status=clarification_required. Present the choice to the user and re-call with their answer. Results are written back into the uploaded file: the response carries file_key, a signed file_url, and a small preview. Each pair adds address, pincode, landmark and status columns.

NameTypeReqDescription
accept_low_precisionboolean––
coordinate_pairsnull|array––
file_keystring––
force_newboolean––
job_idstring––
latitude––one point's latitude in decimal degrees, e.g. 28.6129 (a string is accepted too)
latitude_columnstring––
latlong_columnstring––
longitude––one point's longitude in decimal degrees, e.g. 77.2295 (a string is accepted too)
longitude_columnstring––
sheetstring––

No output schema declared.

No examples provided.

territory_mapping ~753

Run the territory-management pipeline on a branch file uploaded via upload_file. Hybrid async with three modes: pass file_key to START a job (returns a job_id immediately); pass only job_id on subsequent calls to POLL progress; pass job_id AND catchment_type together to RESUME a job that paused for clarification. The pipeline validates that all branches are in one state, computes each branch's isochrone at catchment_distance_km, finds villages (catchment_type='village') or pincodes (catchment_type='pincode') that overlap the isochrone by ≥50%. A village/pincode inside several catchments is kept under EVERY branch (never deduplicated), and the last column closest_branch names the nearest branch by driving distance for those shared units (blank otherwise). Each catchment is split into 5 wedges of 72° (group_number 1-5); each wedge is split into bunches of 1-5 neighbouring units (bunch_number 1..N); each bunch is sequenced via the Trips API (trip_number 1-5); s_no numbers each branch's rows 1..N in that order. Returns a signed URL to an XLSX (download_url) with a Territory sheet of rows and a Maps sheet, and maps: one SVG per branch (map_url) with the branch at the centre, its units shaded by group_number and labelled by s_no, overlaps hatched green (this branch is closest) or red (another branch is closer); render_map=false skips the maps. Optional at start: style_request (the user's words for the map colours, e.g. 'groups in pink shades'; only the 5 group colours and the near/far hatch colours change, applied exactly as asked, pincode maps only) and map_title (replaces the map title). If requested colours make the hatching hard to see, warnings carry a suggestion to pass on to the user. catchment_type is OPTIONAL at start: if omitted, the geo-match service detects the branch file's place columns (a pincode column means pincode, a village column means village), and a catchment_type / area_type / mapping_type column also counts (must be uniform across rows). If the fi…

NameTypeReqDescription
catchment_distance_kmnumber––
catchment_typestring––
file_keystring––
job_idstring––
map_titlestring––
render_mapnull|boolean––
style_requeststring––
NameTypeReqDescription
clarification_messagestring––
clarification_neededboolean––
download_urlstring––
error_codestring––
error_messagestring––
guidancenull|object––
job_idstringyes–
mapsnull|array––
percentintegeryes–
phasestringyes–
poll_after_secondsinteger––
processed_branchesinteger––
statestring––
total_branchesinteger––
warningsnull|array––

No examples provided.

upload_file ~387

Upload a CSV or XLSX file for server-side ingestion under policy (auth, size cap, malware scan, injected-intent scan) and receive a file_key. This is the first step for ANY tool that works on the user's file: question_to_map, geocode, reverse_geocode, pincode_lookup and compute_column all take the returned file_key. When the user names a local CSV/XLSX and wants results added to it (pincodes, cities, coordinates, a computed column), upload it here rather than reading it yourself. Step 1: Call upload_file with file_name, file_size, and question. The response contains a signed upload_url and a curl command — run the curl command to POST the file bytes. The curl response contains file_key, columns, a row preview, and optionally 'intent' (geo-match service detected geo_column, geo_level, value_column, map_type, confidence) and 'guidance' (a ready-to-fire question_to_map action with all detected parameters pre-filled). Forward the intent fields into question_to_map to skip auto-detection and render immediately. For multi-sheet XLSX: the curl response is 'sheet_selection_required' with a file_key and sheets list. Pass file_key and sheet to question_to_map (or any other tool that accepts file_key) — do not call upload_file again. After upload, pass the returned file_key to question_to_map to render a map from the full dataset. The file_key is reusable — for additional questions on the same file, pass the same file_key again without re-uploading. When the upload response includes 'guidance', use its next_actions directly for a zero-round-trip render.

NameTypeReqDescription
file_keystring––
file_namestringyes–
file_sizeintegeryes–
questionstring––
sheetstring––

No output schema declared.

No examples provided.

Install

How do I install the LatLong Maps MCP server?

LatLong Maps is a hosted endpoint at https://geocp.latlong.ai/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 · geocp.latlong.ai

# add to Claude Code
claude mcp add --transport http ai-latlong-map-mcp 'https://geocp.latlong.ai/mcp/'
Common questions

What is the LatLong Maps MCP server?

LatLong Maps is an MCP server listed in the public MCP registry as ai.latlong/map-mcp. Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language. This page covers its hosted endpoint (https://geocp.latlong.ai/mcp/).

Is the LatLong Maps MCP server safe to use?

LatLong Maps scores 69 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 LatLong Maps MCP server expose?

LatLong Maps exposes 8 tools: compute_column, geocode, get_capabilities, pincode_lookup, question_to_map, and 3 more. Their descriptions and schemas cost roughly 3,099 tokens of context every time the server is loaded.

Does the LatLong Maps MCP server require authentication?

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

Is the LatLong Maps MCP server still maintained?

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

What did VerifyMCP test on the LatLong Maps MCP server?

VerifyMCP ran 11 checks on LatLong Maps, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about LatLong Maps: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.