Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Boundr is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http boundr-mcp https://mcp.boundr.dev/mcp
# 2 — ask your agent for something these tools do
# list_boundary_type_codes, search_boundaries_by_name, find_boundaries_at_point and 4 more
Boundr costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
danielinniss1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http boundr-mcp https://mcp.boundr.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Full or partial boundary name. Case-insensitive. Examples: "Hackney", "Greater Manchester", "York", "Kent". |
| boundary_type | no | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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). |
| boundary_types | no | Optional list of type codes to restrict results, e.g. ["CTY", "LBO"]. All levels are returned if omitted. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E09000012". Case-insensitive — "e09000012" resolves to the same boundary. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E09000012" for Hackney. Case-insensitive. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive. |
| tolerance | number | no | Simplification tolerance in degrees (WGS-84). Default 0.0001. Increase to 0.001 for county-scale boundaries. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | ONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Boundr or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Boundr can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.