Robin Saige we check the tools AI agents call

bimhouse

house.bim/bimhouse

bim.house — words become buildings. Generate BIM, check code & structure, quote materials.

— the operator's own registry description reported

Publisher house.bim · first seen 2026-08-12 · endpoint https://bim.house/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
29
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 29 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster mid-solo · distinctiveness 0.257 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency305 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools29
vs populationmid
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_e713aaad9923abf12e187b38 · 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?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-solo · 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-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-14outcomeok_tools (was http_error)
2026-08-12outcomefirst probe: http_error

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
action17changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public7serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified4not classifiable from its textTier-1 only until its tools describe themselves
retrieval-private1serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies

Tools last seen observed

admin_set_site_context chat create_house create_product delete_zoning_rule get_build_plan get_houki_rules get_house_bim get_product get_site_context houki_check list_contractors list_houses list_incomplete_addresses list_mine match_contractors material_quote place_in_house place_order register_contractor retire_product search_catalog set_forkable set_site_context set_visibility update_house update_product upsert_zoning_rule whoami

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 & specific29/29
has a description29/29
description is substantive29/29
parameters are typed29/29
parameters are described28/2928/29

29 of 29 tools graded · 29 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
1.0.0
server version bim.house

Capabilities: tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:49Zok_tools2003052025-06-18
2026-08-12T05:34:03Zhttp_error525324

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/house.bim/bimhouse.svg)](https://robinsaige.com/s/house.bim/bimhouse)

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