bharatlas-mcp

MCPcommunity
v1.3.0io.github.sathya-sankaranMITUpdated 5d agonpmGitHub

Query India's open geo data, and author collect maps: register a link, moderate, publish.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
58Downloads/wk
38GitHub stars
3Forks
5d agoLast update
Package
Authorio.github.sathya-sankaran
LicenseMIT
Version1.3.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface17 tools · 1 privileged
Security scan✓ Cleanv1.1.1 · 22d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

17 tools · 1 privileged
Statically extracted from the published packagev1.1.1 · 22d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_layersList available geo layers. Use to discover what data bharatlas has.

List available geo layers. Use to discover what data bharatlas has.

No input schema was published for this tool.

get_layer_schemaGet column names, types, and sample values for a layer.

Get column names, types, and sample values for a layer.

No input schema was published for this tool.

query_layerQuery a layer's data with filters and grouping. Reads the parquet file at runtime.

Query a layer's data with filters and grouping. Reads the parquet file at runtime.

No input schema was published for this tool.

locateGiven a latitude/longitude, find which administrative boundaries, zones, and regions

Given a latitude/longitude, find which administrative boundaries, zones, and regions

No input schema was published for this tool.

nearbyFind features from a layer that are near a given point. Samples a grid of points around the

Find features from a layer that are near a given point. Samples a grid of points around the

No input schema was published for this tool.

list_categoriesList all data categories with layer counts.

List all data categories with layer counts.

No input schema was published for this tool.

get_layer_detailGet full metadata for a single layer: download URLs (parquet, pmtiles, geojson, kml, shapefile),

Get full metadata for a single layer: download URLs (parquet, pmtiles, geojson, kml, shapefile),

No input schema was published for this tool.

list_submissionsList community-submitted geo layers. These are user-contributed datasets

List community-submitted geo layers. These are user-contributed datasets

No input schema was published for this tool.

register_mapRegister a collect map so this server can act on it. Paste the whole share link

Register a collect map so this server can act on it. Paste the whole share link

No input schema was published for this tool.

list_my_mapsList the collect maps you have registered here (local store), each with its scope.

List the collect maps you have registered here (local store), each with its scope.

No input schema was published for this tool.

get_mapA collect map's metadata + record counts, plus a link to open it in collect. Any registered scope.

A collect map's metadata + record counts, plus a link to open it in collect. Any registered scope.

No input schema was published for this tool.

get_recordsA collect map's records as a GeoJSON FeatureCollection — for reading, analysis, or backup/export.

A collect map's records as a GeoJSON FeatureCollection — for reading, analysis, or backup/export.

No input schema was published for this tool.

moderate_recordApprove or reject one pending point (needs the admin link). Pass the map id it belongs to.

Approve or reject one pending point (needs the admin link). Pass the map id it belongs to.

No input schema was published for this tool.

import_pointsBulk-import points you already hold into a collect map (needs the admin link). NOT for synthetic data.

Bulk-import points you already hold into a collect map (needs the admin link). NOT for synthetic data.

No input schema was published for this tool.

edit_mapprivilegedEdit a collect map's settings: name/description/purpose/category/data_year/basemap (needs the admin link).

Edit a collect map's settings: name/description/purpose/category/data_year/basemap (needs the admin link).

No input schema was published for this tool.

publishBake a collect map's approved points into a bharatlas catalog submission (needs the admin link).

Bake a collect map's approved points into a bharatlas catalog submission (needs the admin link).

No input schema was published for this tool.

create_mapOptional: create a collect map programmatically. Most maps are made online at collect.bharatlas.com (no key needed) —

Optional: create a collect map programmatically. Most maps are made online at collect.bharatlas.com (no key needed) —

No input schema was published for this tool.

17 of 17 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Query India's open geo data, and author collect maps: register a link, moderate, publish.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-20 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.