Robin Saige we check the tools AI agents call

DaedalMap Administrative Boundaries (loc_id to polygon)

com.daedalmap/boundaries

A loc_id to its bounding box, centroid, and polygon, with its name and admin level.

— the operator's own registry description reported

Publisher com.daedalmap · first seen 2026-08-12 · endpoint https://app.daedalmap.com/mcp/boundaries

allow
verdict
gateway
cluster
ok_tools
answers
11
tools served

Dependency rating derived

allow — gateway — safe to depend on

Cluster gateway · distinctiveness 0.442 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency65 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools11
vs populationmid
capabilities3
harnessA
Trust — can it rely on it?
identityfarm_member
servers on its host17
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_8b6164bc758599eafdb53738 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

check_geometry compare_geographies create_geometry_export estimate_geometry_package get_catalog get_geometry get_job_status get_pack get_tool_help loc_id_info resolve_loc_id_scope

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific11/11
has a description11/11
description is substantive11/11
parameters are typed11/11
parameters are described8/118/11

11 of 11 tools graded · 11 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
0.4.0
server version com.daedalmap/boundaries

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-08-14inventorytools 10 → 11
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:02Zok_tools200652025-06-18
2026-08-12T05:33:18Zok_tools200512025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.daedalmap/boundaries.svg)](https://robinsaige.com/s/com.daedalmap/boundaries)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview