Robin Saige we check the tools AI agents call

ikeytz Einsatzgebiet-Karten

com.ikeytz/maps

Read/Link MCP for maps.ikeytz.com. Public read-only. No forms. ai-train=no.

— the operator's own registry description reported

Publisher com.ikeytz · first seen 2026-08-30 · endpoint https://maps.ikeytz.com/mcp

allow
verdict
rich-shared
cluster
ok_tools
answers
67
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 67 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster rich-shared · distinctiveness 0.78 (unusual). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency319 ms
vs populationtypical
protocolleading
authopen
Can it be used? Q4 · observed
tools67
vs populationhigh
capabilities4
harnessA
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host1
servers on its domain2
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_6da070db3d2f160d74e5b752 · 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.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-shared · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-30 → 2026-09-06). 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-09-06inventorytools 66 → 67
2026-08-30outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public58serves public factstruth-checkable against a public source — the V-ladder applies in full
generative8creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

compose_mailto compose_tel_landline compose_tel_mobile compose_whatsapp distance_to_office find_by_area find_by_gebiet find_by_geo find_by_google_maps find_by_icbm find_by_keyword find_by_plz find_by_serp get_about get_agb get_ai_page get_ai_txt get_auswahl_item get_business_identity get_contact get_copyright get_datenschutz get_discovery get_embed_map get_emergency get_faq get_geo_api get_geo_office get_geschichte get_grenze get_hub get_impressum get_invoice_line_items get_lage get_legal get_links get_llms_mcp_server get_llms_mcp_web get_llms_txt get_nutzungsbedingungen get_ort_datetime get_page_summary get_partner_info get_prices get_ratgeber get_review_url get_serp_snippet get_service_area get_sitemap_txt get_urheberrecht get_widerruf get_wissen_entry list_auswahl list_faq list_footer list_locales list_nav list_plz list_ratgeber list_service_areas list_services list_slugs list_whatsapp_options list_wissen resolve_locale_url resolve_maps_url site_overview

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 & specific67/67
has a description67/67
description is substantive67/67
parameters are typed67/67
parameters are described67/67

67 of 67 tools graded · 67 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-11-25
protocol version
session model
1.0.0
server version ikeytz-maps

Capabilities: logging prompts resources tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:12:32Zok_tools2003192025-11-25
2026-08-30T06:12:16Zok_tools2003192025-11-25

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.ikeytz/maps.svg)](https://robinsaige.com/s/com.ikeytz/maps)

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

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →