Boundr
REMOTE · MCP.BOUNDR.DEV · SCANNED SEP 20
UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries
Available components
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the Boundr MCP server?
Boundr is a hosted endpoint at https://mcp.boundr.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.boundr.dev
claude mcp add --transport http danielinniss-boundr 'https://mcp.boundr.dev/mcp'
{
"mcpServers": {
"danielinniss-boundr": {
"url": "https://mcp.boundr.dev/mcp"
}
}
} {
"servers": {
"danielinniss-boundr": {
"type": "http",
"url": "https://mcp.boundr.dev/mcp"
}
}
} [mcp_servers.danielinniss-boundr] url = "https://mcp.boundr.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"danielinniss-boundr": {
"type": "remote",
"url": "https://mcp.boundr.dev/mcp",
"enabled": true
}
}
} openclaw mcp add danielinniss-boundr --url 'https://mcp.boundr.dev/mcp' --transport streamable-http
mcp_servers:
danielinniss-boundr:
url: "https://mcp.boundr.dev/mcp" {
"McpServers": {
"danielinniss-boundr": {
"Transport": "http",
"Url": "https://mcp.boundr.dev/mcp"
}
}
} assistant mcp add danielinniss-boundr -t streamable-http -u 'https://mcp.boundr.dev/mcp'
{
"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.
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.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 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 | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | afeab3569725998f13bac3e0e17b88d0 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| boundary_types | – | – | Optional list of type codes to restrict results, e.g. ["CTY", "LBO"]. All levels are returned if omitted. |
| lat | number | yes | Latitude in decimal degrees. Must be between -90 and 90. Example: 51.5074 (central London). |
| lng | number | yes | Longitude in decimal degrees. Must be between -180 and 180. Example: -0.1278 (central London). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E09000012". Case-insensitive — "e09000012" resolves to the same boundary. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E09000012" for Hackney. Case-insensitive. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive. |
| tolerance | number | – | Simplification tolerance in degrees (WGS-84). Default 0.0001. Increase to 0.001 for county-scale boundaries. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| boundary_type | – | – | Optional 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. |
| name | string | yes | Full or partial boundary name. Case-insensitive. Examples: "Hackney", "Greater Manchester", "York", "Kent". |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the Boundr MCP server?
Boundr is an MCP server listed in the public MCP registry as io.github.danielinniss/boundr. UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries. This page covers its hosted endpoint (https://mcp.boundr.dev/mcp).
Is the Boundr MCP server safe to use?
Boundr scores 80 out of 100 on VerifyMCP. 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 Boundr MCP server expose?
Boundr exposes 7 tools: list_boundary_type_codes, search_boundaries_by_name, find_boundaries_at_point, get_boundary_by_code, get_boundary_geojson_by_code, and 2 more. Their descriptions and schemas cost roughly 1,427 tokens of context every time the server is loaded.
Does the Boundr MCP server require authentication?
No. We connected to Boundr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Boundr MCP server still maintained?
Boundr is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.