Boundr
UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries
| Endpoint | https://mcp.boundr.dev/mcp (streamable-http) |
|---|---|
| Registry version | 1.1.0 |
| Now | 7 tools · grade B (81) · pin ts_f289ba2443e0102ce37ebca6334d8a84 · protocol 2025-06-18 |
| First / last listed | 2026-11-02 03:15 UTC / 2026-11-02 03:15 UTC |
| Grade over time | 2026-11-02: B (81), 7 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: list_boundary_type_codes search_boundaries_by_name find_boundaries_at_point get_boundary_by_code get_boundary_geojson_by_code get_boundary_geojson_simplified get_boundary_bbox
list_boundary_type_codes | Returns every valid UK boundary type code mapped to its human-readable label.
Call this before using any tool that accepts a `boundary_type` or
`boundary_types` argument so you know which codes are legal. Passing an
unlisted code to another tool raises a ValueError.
Boundary type codes are stable Ordnance Survey identifiers. Common ones:
- "CTY" → County
- "LBO" → London Borough
- "UTA" → Uni params: none |
search_boundaries_by_name | Search for UK administrative boundaries by name (case-insensitive partial match).
Use this to discover boundaries when you have a place name but not a code.
Returns lightweight metadata only — no geometry. If you need to display or
analyse the boundary shape, call get_boundary_geojson_by_code() with the
returned `code`.
Call list_boundary_type_codes() first if you need to filter by type and are
params: name*, boundary_type |
find_boundaries_at_point | Find all UK administrative boundaries that geographically contain a coordinate point.
Use this to answer "what county/borough/ward is this location in?" for a
latitude/longitude. Returns lightweight metadata only — no geometry. If you
need to display a boundary shape, call get_boundary_geojson_by_code() with
the returned `code`.
Multiple boundaries at different administrative levels typically co params: lat*, lng*, boundary_types |
get_boundary_by_code | Look up metadata for a single UK boundary by its ONS census code. No geometry.
Use this when you already have a census code (e.g. from
search_boundaries_by_name() or find_boundaries_at_point()) and need
structured metadata such as area size or type label. If you also need the
boundary shape for display or analysis, call get_boundary_geojson_by_code()
instead.
ONS census codes (sometimes called G params: code* |
get_boundary_geojson_by_code | Fetch the full GeoJSON geometry for a UK boundary by its ONS census code.
Returns a GeoJSON Feature object (WGS-84 / EPSG:4326) suitable for
rendering on a map or performing geometric analysis. The geometry can be
large — county and ceremonial county polygons are especially heavy. Only
call this when you specifically need the shape; for metadata only use
get_boundary_by_code() instead.
IMPORTANT params: code* |
get_boundary_geojson_simplified | Fetch simplified GeoJSON for a boundary by its ONS census code.
Safe to embed directly in generated HTML map files. At the default tolerance
(0.0001°) a constituency polygon shrinks from ~4,000 vertices to ~200–400
with no visible difference at normal map zoom levels.
Prefer this over get_boundary_geojson_by_code() when writing Leaflet map
pages — the full geometry is large enough to exhaust you params: code*, tolerance |
get_boundary_bbox | Get the bounding box and centroid for a boundary by its ONS census code.
Returns min_lat, max_lat, min_lng, max_lng, centroid_lat, centroid_lng.
Pass the bbox values directly to Knotsure's sightings_in_bbox() or
geographic_summary(). Much cheaper than get_boundary_geojson_by_code() for
spatial queries because no geometry is fetched or serialised. params: code* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.