Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Boundr

REMOTE · MCP.BOUNDR.DEV · SCANNED AUG 3

UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries

Available components

+4 this week 68 Trust /100
Trust breakdown (6 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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1427 tokens (~203/item across 7 items; 7 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.boundr.dev

# add to Claude Code
claude mcp add --transport http danielinniss-boundr https://mcp.boundr.dev/mcp
# ~/.codex/config.toml
[mcp_servers.danielinniss-boundr]
url = "https://mcp.boundr.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danielinniss-boundr": {
      "type": "remote",
      "url": "https://mcp.boundr.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add danielinniss-boundr --url https://mcp.boundr.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  danielinniss-boundr:
    url: "https://mcp.boundr.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "danielinniss-boundr": {
      "type": "http",
      "url": "https://mcp.boundr.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 63

    First indexed and scored.

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 3 Aug 2026 · Probed https://mcp.boundr.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=boundr.dev CN=WE1,O=Google Trust Services,C=US 10 Jul 2026 8 Oct 2026 ECDSA 256 ECDSA-SHA256 ce7c995ff17dea83131da3c878ebd843
SANs: boundr.dev, *.boundr.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of mcp.boundr.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
boundr.dev. absent 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=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.boundr.dev/mcp Verified 200
http (plaintext) http://mcp.boundr.dev/mcp HTTPS enforced 308 https://mcp.boundr.dev/mcp
MCP tools — 7 exposed · ~1,427 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.

Tool Tokens
find_boundaries_at_point ~229

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 contain the same point (e.g. a ward, a borough, and a county). Filter by boundary_types to restrict which levels are returned. Call list_boundary_type_codes() first if you are unsure which type codes to use.

NameTypeReqDescription
boundary_typesOptional list of type codes to restrict results, e.g. ["CTY", "LBO"]. All levels are returned if omitted.
latnumberyesLatitude in decimal degrees. Must be between -90 and 90. Example: 51.5074 (central London).
lngnumberyesLongitude in decimal degrees. Must be between -180 and 180. Example: -0.1278 (central London).
NameTypeReqDescription
resultarrayyes

No examples provided.

get_boundary_bbox ~126

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.

NameTypeReqDescription
codestringyesONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive.
NameTypeReqDescription
resultyes

No examples provided.

get_boundary_by_code ~202

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 GSS codes or LAU codes) are stable identifiers of the form "E09000012" (Hackney), "E10000016" (Kent), etc. The first letter indicates the country: E = England, W = Wales, S = Scotland, N = Northern Ireland.

NameTypeReqDescription
codestringyesONS census / GSS / LAU code, e.g. "E09000012". Case-insensitive — "e09000012" resolves to the same boundary.
NameTypeReqDescription
resultyes

No examples provided.

get_boundary_geojson_by_code ~253

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 — Leaflet / web maps: use get_boundary_geojson_simplified() instead. The full geometry is large enough to exhaust your context window before you can finish writing the page. The simplified version is safe to embed directly in HTML and indistinguishable from the full shape at normal map zoom levels. Use this tool only when you need full-fidelity geometry for server-side analysis (e.g. precise point-in-polygon checks, area calculations, clipping). Obtain the census code from search_boundaries_by_name() or find_boundaries_at_point() before calling this.

NameTypeReqDescription
codestringyesONS census / GSS / LAU code, e.g. "E09000012" for Hackney. Case-insensitive.
NameTypeReqDescription
resultyes

No examples provided.

get_boundary_geojson_simplified ~185

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 your context window before you can finish writing the HTML.

NameTypeReqDescription
codestringyesONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive.
tolerancenumberSimplification tolerance in degrees (WGS-84). Default 0.0001. Increase to 0.001 for county-scale boundaries.
NameTypeReqDescription
resultyes

No examples provided.

list_boundary_type_codes ~249

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" → Unitary Authority - "MTD" → Metropolitan District - "DIS" → District - "DIW" → District Ward - "CCTY" → Ceremonial County - "HCTY" → Historic County - "WMC" → Westminster Parliamentary Constituency - "GLC" → Greater London Constituency - "SWC" → Scotland/Wales Constituency - "PAR" → Parish - "CED" → County Electoral Division Returns: Dict mapping code → label for all supported boundary types, e.g. {"CTY": "County", "LBO": "London Borough", ...}

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

search_boundaries_by_name ~183

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 unsure which code to use.

NameTypeReqDescription
boundary_typeOptional type code to narrow results, e.g. "LBO" for London Boroughs or "CTY" for Counties. Must be a code from list_boundary_type_codes(); raises ValueError otherwise.
namestringyesFull or partial boundary name. Case-insensitive. Examples: "Hackney", "Greater Manchester", "York", "Kent".
NameTypeReqDescription
resultarrayyes

No examples provided.