Skip to content

Boundr MCP server

io.github.danielinniss/boundrdanielinnissstreamable-httpv1.1.0Scanned

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

7 tools: 4 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Boundr MCP server can do

The Boundr MCP server is published by the GitHub account danielinniss. It has 7 tools. It can create or change data (4 tools: get_boundary_by_code, get_boundary_geojson_by_code, get_boundary_geojson_simplified and get_boundary_bbox), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 4Claude Code: ask
  • get_boundary_bboxGet the bounding box and centroid for a boundary by its ONS census code.No findings

    Why it is in this group

    • The name "get_boundary_bbox" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • get_boundary_by_codeLook up metadata for a single UK boundary by its ONS census code.No findings

    Why it is in this group

    • The name "get_boundary_by_code" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • get_boundary_geojson_by_codeFetch the full GeoJSON geometry for a UK boundary by its ONS census code.No findings

    Why it is in this group

    • The name "get_boundary_geojson_by_code" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • get_boundary_geojson_simplifiedFetch simplified GeoJSON for a boundary by its ONS census code.No findings

    Why it is in this group

    • The name "get_boundary_geojson_simplified" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
Only reads 3Show 3 read-only tools
  • find_boundaries_at_pointFind all UK administrative boundaries that geographically contain a coordinate point.No findings

    Why it is in this group

    • The name "find_boundaries_at_point" says "find": a word for reading.
    Description, as the server wrote it
    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.
  • list_boundary_type_codesReturns every valid UK boundary type code mapped to its human-readable label.No findings

    Why it is in this group

    • The name "list_boundary_type_codes" says "list": a word for reading.
    Description, as the server wrote it
    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_nameSearch for UK administrative boundaries by name (case-insensitive partial match).No findings

    Why it is in this group

    • The name "search_boundaries_by_name" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.boundr.dev/mcp: tools/list returned 7 tools to an anonymous client, including get_boundary_by_code (write), get_boundary_geojson_by_code (write), get_boundary_geojson_simplified (write), get_boundary_bbox (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__boundr__list_boundary_type_codes",
      "mcp__boundr__search_boundaries_by_name",
      "mcp__boundr__find_boundaries_at_point"
    ],
    "ask": [
      "mcp__boundr__get_boundary_by_code",
      "mcp__boundr__get_boundary_geojson_by_code",
      "mcp__boundr__get_boundary_geojson_simplified",
      "mcp__boundr__get_boundary_bbox"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as boundr. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.danielinniss/boundr/verify?hash=61005bd183b91dc4941a9236ee553b88e87333c81dec0967a256e8c449e9ed04" | jq -e '.changed == false'

Pinned hash 61005bd183b9, from Nov 16, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.danielinniss/boundr/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.danielinniss/boundr
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.danielinniss/boundr.svg)](https://radar.anlyon.com/servers/io.github.danielinniss/boundr)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:29 UTC.

Boundr MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Boundr MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Boundr MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Boundr MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Boundr MCP server have?

7 tools: 4 write, 3 read. get_boundary_by_code, get_boundary_geojson_by_code, get_boundary_geojson_simplified, get_boundary_bbox, list_boundary_type_codes, search_boundaries_by_name and find_boundaries_at_point.

Does the Boundr MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Boundr MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Boundr MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.