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.

io.github.urbanmorph/bharatlas-mcp

NPM · BHARATLAS-MCP

Query India's open geo data. Locate, filter, nearby search across layers.

Available components

0 this week 77 Trust /100

Last scanned (22 hours ago)

Scores higher than 56% of npm servers

Category Maps and Location

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Moved to io.github.sathya-sankaran/bharatlas-mcp.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2076 tokens (~259/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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.93 functional
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 · Analysed npm/bharatlas-mcp@1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~960 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
get_layer_detail ~56

Get full metadata for a single layer: download URLs (parquet, pmtiles, geojson, kml, shapefile), attribution, license, feature count, and level metadata.

NameTypeReqDescription
layer_idstringyesLayer ID

No output schema declared.

No examples provided.

get_layer_schema ~73

Get column names, types, and sample values for a layer. Use BEFORE querying to discover what columns exist and what values they contain. Essential for knowing the right column names for filters.

NameTypeReqDescription
layer_idstringyesLayer ID (e.g. lgd_states, airports, soi_forests, wards_chennai)

No output schema declared.

No examples provided.

list_categories ~16

List all data categories with layer counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_layers ~204

List available geo layers. Use to discover what data bharatlas has. Returns layer IDs, names, row counts, categories, and download formats. Filter by category (boundaries, city-wards, environment, water, agriculture, transport, etc.), admin level (state, district, block, village, etc.), source, or text search.

NameTypeReqDescription
categorystring–Filter by category: boundaries, city-wards, people, environment, water, agriculture, transport, infrastructure, health-edu
levelstring–Filter by admin level: state, district, subdistrict, block, village, etc.
limitnumber–Max results (default 20)
offsetnumber–Skip N results for pagination
qstring–Text search across layer IDs, sources, and descriptions
sourcestring–Filter by data source: LGD, SOI, Bhuvan, OpenCity, DataMeet, etc.

No output schema declared.

No examples provided.

list_submissions ~90

List community-submitted geo layers. These are user-contributed datasets under open licenses. Filter by category or search by name.

NameTypeReqDescription
categorystring–Filter by category
limitnumber–Max results (default 20)
offsetnumber–Pagination offset
qstring–Search name and description
sortstring–Sort order (default: recent)

No output schema declared.

No examples provided.

locate ~129

Given a latitude/longitude, find which administrative boundaries, zones, and regions contain that point. Returns state, district, subdistrict, block, parliament/assembly constituency, pincode, seismic zone, high court jurisdiction, and more. The 'where am I?' tool. Also accepts specific layer IDs to check.

NameTypeReqDescription
latnumberyesLatitude (6 to 38, India bounding box)
layersarray–Specific layer IDs to check (default: 12 essential layers covering all admin levels + zones)
lngnumberyesLongitude (68 to 98, India bounding box)

No output schema declared.

No examples provided.

nearby ~167

Find features from a layer that are near a given point. Samples a grid of points around the center and checks which hit the target layer via locate. Generic: works for any layer type (polygons, points, lines) without needing coordinate columns. Example: 'reservoirs near Bengaluru' -> layer_id: 'wris_reservoirs', lat: 12.97, lng: 77.59, radius_km: 50.

NameTypeReqDescription
latnumberyesCenter point latitude
layer_idstringyesLayer to search for nearby features
limitnumber–Max results (default 20)
lngnumberyesCenter point longitude
radius_kmnumber–Search radius in kilometres (default 25, max 200)

No output schema declared.

No examples provided.

query_layer ~225

Query a layer's data with filters and grouping. Reads the parquet file at runtime. Supports: select specific columns, filter by column values, group by a column to get counts. Use get_layer_schema first to discover column names. Examples: 'airports in Karnataka' -> where: {state: 'KA'}, 'forest types' -> group_by: 'type', 'health facilities in Bihar' -> where: {state: 'BIHAR'}, select: ['name', 'type'].

NameTypeReqDescription
group_bystring–Column to group by. Returns {value: count} instead of rows.
include_centroidboolean–Include _lat/_lng centroid coordinates (defaults to true). Set false to exclude.
layer_idstringyesLayer ID to query
limitnumber–Max rows (default 100, max 1000)
selectarray–Column names to return. Omit for all non-geometry columns.
whereobject–Filter conditions as {column: value} pairs. Case-insensitive matching.

No output schema declared.

No examples provided.

Install

How do I install the io.github.urbanmorph/bharatlas-mcp server?

io.github.urbanmorph/bharatlas-mcp runs locally as an npm package, launched with npx -y bharatlas-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · bharatlas-mcp

# add to Claude Code
claude mcp add urbanmorph-bharatlas-mcp -- npx -y bharatlas-mcp
Common questions

What is the io.github.urbanmorph/bharatlas-mcp server?

io.github.urbanmorph/bharatlas-mcp is listed in the public MCP registry as io.github.urbanmorph/bharatlas-mcp. Query India's open geo data. Locate, filter, nearby search across layers. This page covers its npm package (bharatlas-mcp).

Is the io.github.urbanmorph/bharatlas-mcp server safe to use?

io.github.urbanmorph/bharatlas-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.urbanmorph/bharatlas-mcp server expose?

io.github.urbanmorph/bharatlas-mcp exposes 8 tools: list_layers, get_layer_schema, query_layer, locate, nearby, and 3 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.

Is the io.github.urbanmorph/bharatlas-mcp server still maintained?

io.github.urbanmorph/bharatlas-mcp is marked deprecated 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 licence is the io.github.urbanmorph/bharatlas-mcp server under?

io.github.urbanmorph/bharatlas-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.urbanmorph/bharatlas-mcp server?

VerifyMCP ran 16 checks on io.github.urbanmorph/bharatlas-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.