Pakistan Land Parcels & Khasra Lookup (پنجاب اراضی)
Server Details
Punjab (Pakistan) urban parcels from PULSE by parcel code, housing society or point, with land use.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- BumiAtlas/pakistan-land-parcels-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools split cleanly along retrieve-records vs. render-map lines, and each description explicitly points to the other ('Use PK_parcel_image to see a parcel and its neighbours'). The only minor overlap is that the image tool also returns in-view parcels as JSON, but its primary output (JPEG maps) is unmistakably different from a record search.
Both names follow a stable `PK_parcel_<suffix>` pattern with the same domain prefix and resource noun, which makes them easy to group and scan. The suffixes mix a verb ('search') with a noun ('image'), a small inconsistency but still predictable and readable.
Two tools is thin for a lookup server, but each is heavily parameterised (multi-basemap rendering, code/society/coordinate search modes) so the surface is not trivial. Still, with only a search and an image tool there is no room for auxiliary operations like listing societies or districts.
Core workflow—find a parcel by code, society, or coordinates, then see it on a map—is fully covered, including optional GeoJSON geometry. However, there is no way to enumerate available societies, tehsils, districts, or source layers, so an agent must guess valid query values, and the server's namesake khasra lookup is only reachable indirectly through search results.
Available Tools
2 toolsPK_parcel_imageMap image of a Punjab parcel and its neighboursARead-onlyIdempotentInspect
A map image centred on a Punjab parcel (id, or its uniParco code) or a point (query), with every parcel in view outlined and labelled with its khasra plot number, so you can see which parcel is where. The parcel passed as id is drawn in red with a larger label; a query point is a red dot. Returns the parcels in view as JSON (label, id, uniParco, society, landuse, area in m²; labelled: false where its label didn't fit), then one JPEG per basemap. Basemaps: satellite (Esri World Imagery, often a few years old), hybrid (the same imagery with road and place names), streets and topo (Esri's street and topographic maps). Pass several to compare, e.g. ['satellite', 'streets'] to match buildings with street names. Parcel outlines are yellow on imagery and magenta on maps. PULSE linework is indicative: offsets of several metres from both imagery and the legal boundary are normal. A scale bar is at bottom left. Labels are left off where they'd overlap; call again with a smaller radius to read them. Each image costs about as much context as 1,000 words, so ask for what you need.
Inputs: id, size, query, radius, +1 more.
PK_parcel_searchSearch Punjab (Pakistan) land parcelsARead-onlyIdempotentInspect
Find urban Punjab parcels (PULSE development-authority data) by parcel code, society name, or location, with each parcel's whole record. query takes a parcel code ('TXL-TEH-00C-000-0157-0000'; a prefix like 'MDT-TNS' lists that tehsil's or mouza's parcels), a housing society name or part of one ('DHA', 'Millat Town'), or coordinates as 'latitude, longitude' (e.g. 31.4726, 74.2728). With coordinates it returns parcels containing the point (distance 0), then the nearest within radius metres, closest first. Society and prefix searches list parcels paged with offset. Each parcel has id, uniParco, khasra (plot number), plotNo, block, sector, phase, society, source (which authority's layer), landuse, landuseSub, plotSize, area and mapArea (m²), anomaly (PULSE's data-quality flag), district, tehsil, division and bbox. Set include_geometry for each boundary as GeoJSON (keep limit small). Use PK_parcel_image to see a parcel and its neighbours.
Inputs: query (required), limit, offset, radius, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Indian khasra and survey parcels in five states by coordinates, ULPIN or number in a village.
Austrian BEV cadastral parcels by KG and Grundstücksnummer or coordinates, with land uses.
Beninese ANDF cadastral parcels by NUP, titre foncier or coordinates, with declared zones.
Burkinabè DGI eCadastre parcels by commune, section, îlot and parcel, or coordinates.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRead-only access to Portugal’s official property cadastre (DGT Cadastro Predial): look up a parcel by map point, list parcels in a municipality, or check coverage. Accent-insensitive municipality names. Covers only 118 municipalities; Porto has no parcels, Lisboa only isolated records. Data: CC BY 4.0, Direção-Geral do Território. Not an official certificate (not a certidão or caderneta).MIT
- AlicenseAqualityBmaintenanceOwner, APN and address lookup across 481 US counties (509 verified ArcGIS REST endpoints, all 50 states plus DC), plus code violations and building permits for 30 cities and zoning cases for 19. No API key; built on public county GIS data.41,755 npm1MIT
- AlicenseNot gradedqualityCmaintenanceSearch, query, and explore City of Phoenix open geospatial data (parcels, zoning, public works) via ArcGIS Feature Services.64 npmMIT
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server providing direct, credentialed access to parcel data via Regrid and county ArcGIS sources, with tools for querying by point, owner, size, and county.-
Glama MCP Gateway
Add one secure layer between your agents and this server.