# Boundr (remote · mcp.boundr.dev)

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

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.boundr.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/danielinniss-boundr/mcp.md), [page](https://verifymcp.io/servers/danielinniss-boundr/mcp)

## Channel facts

- Endpoint: `https://mcp.boundr.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http danielinniss-boundr https://mcp.boundr.dev/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add danielinniss-boundr --url https://mcp.boundr.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  danielinniss-boundr:
    url: "https://mcp.boundr.dev/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +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.

### 2026-07-31 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +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.

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (7)

### `list_boundary_type_codes` (~249 tokens)

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", ...}

### `search_boundaries_by_name` (~183 tokens)

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.

Input parameters:

- `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, required): Full or partial boundary name. Case-insensitive. Examples:   "Hackney", "Greater Manchester", "York", "Kent".

Output parameters:

- `result` (array)

### `find_boundaries_at_point` (~229 tokens)

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.

Input parameters:

- `boundary_types`: Optional list of type codes to restrict results,             e.g. ["CTY", "LBO"]. All levels are returned if omitted.
- `lat` (number, required): Latitude in decimal degrees. Must be between -90 and 90.  Example: 51.5074 (central London).
- `lng` (number, required): Longitude in decimal degrees. Must be between -180 and 180.  Example: -0.1278 (central London).

Output parameters:

- `result` (array)

### `get_boundary_by_code` (~202 tokens)

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.

Input parameters:

- `code` (string, required): ONS census / GSS / LAU code, e.g. "E09000012".   Case-insensitive — "e09000012" resolves to the same boundary.

Output parameters:

- `result`

### `get_boundary_geojson_by_code` (~253 tokens)

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.

Input parameters:

- `code` (string, required): ONS census / GSS / LAU code, e.g. "E09000012" for Hackney.   Case-insensitive.

Output parameters:

- `result`

### `get_boundary_geojson_simplified` (~185 tokens)

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.

Input parameters:

- `code` (string, required): 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.

Output parameters:

- `result`

### `get_boundary_bbox` (~126 tokens)

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.

Input parameters:

- `code` (string, required): ONS census / GSS / LAU code, e.g. "E14001592" for Woking.   Case-insensitive.

Output parameters:

- `result`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/danielinniss-boundr/mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://mcp.boundr.dev/mcp
- Repository: https://github.com/danielinniss/boundr
- Website: https://boundr.dev/
- Changelog RSS feed: https://verifymcp.io/servers/danielinniss-boundr/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/danielinniss-boundr/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/danielinniss-boundr/mcp