Robin Saige we check the tools AI agents call

Bilt

io.github.buildingapplications/mcp

AI agents autonomously build and deploy mobile apps through natural language workflows

— the operator's own registry description reported

Publisher io.github.buildingapplications · first seen 2026-08-12 · endpoint https://mcp.bilt.me/mcp/sse

block
verdict
dead-listing
cluster
http_error
answers
tools served

Dependency rating derived

block
block — dead / unreachable · action ○ · V n/a
block — because dead / unreachable ●, no confirmed drift in 2 probes ●; not yet checked: harness, truth (0 runs)

Cluster dead-listing · distinctiveness —. Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersdead_listing
latency660 ms
protocolunknown
authn/a
Can it be used? Q4 · observed
capabilities0
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_3093eb2618c18a2c8d944edd · 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?dead / unreachable — 2 probes ●evidence ↓
Q2What is it?action ○ evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?truth not yet run · no drift ●evidence ↓
Q5What company does it keep?dead-listing · 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 (1 events)
datetypewhat changed
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 the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action1changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions

Tools last seen observed

no tool inventory served

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.

Drift observed

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

Looking for an alternative?

This server doesn't answer, but these live, allow-verdict servers describe themselves similarly — similar by what they say they do — never verified drop-in replacements; check each one before depending on it.

serververdictshared terms
cloud.redu/mcp
Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
allowagents, apps, autonomously, build
io.github.ColinHughes2121/gocreative-agent-api
17-model LLM gateway + 350+ data/KYB/sanctions tools. Pay-per-call USDC via x402, no API key.
allowagents, apps, autonomously, mobile
com.ainetcafe/netcafe-build
Deploy a live web app from one sentence. build_app + poll to a public HTTPS URL you own.
allowapps, autonomously, build, deploy
io.standoutmcp/standout
Anti-slop design taste for AI coding agents: art directions, section code, 0-100 page critic.
allowapps, build, deploy, mobile
com.ainetcafe/ai-netcafe
Tables and ledgers checked by arithmetic, not by a model. 24 tools. MCP 2026-07-28 ready.
allowapps, autonomously, build, deploy
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:26Zhttp_error404660
2026-08-12T05:34:38Zhttp_error404507

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/io.github.buildingapplications/mcp.svg)](https://robinsaige.com/s/io.github.buildingapplications/mcp)

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