Robin Saige we check the tools AI agents call

VaultCrux Platform

io.github.CueCrux/vaultcrux-platform

VaultCrux Platform — 60 tools: retrieval, proof, intel, economy, watch, org

— the operator's own registry description reported

Publisher io.github.CueCrux · first seen 2026-08-12 · endpoint https://api.vaultcrux.com/platform/mcp

allow
verdict
rich-slow-shared
cluster
ok_tools
answers
76
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V1 shows its work ◐
allow — because answers ●, 76 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

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

Does it answer? Q1 · observed
answersalive_tools
latency434 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools76
vs populationhigh
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host2
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_76957863f6c53050b645b3aa · 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?V1 shows its work ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-shared · 2 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: 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-public35serves public factstruth-checkable against a public source — the V-ladder applies in full
action20changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified19not classifiable from its textTier-1 only until its tools describe themselves
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

accept_handoff_package action_journal_query annotate_session browse_bundles change_seat_role comment_on_work create_coalition create_handoff_package create_work cuecrux_session declare_revenue_willingness diff_receipts explain_last_answer find_contradictions forecast_obsolescence get_active_policy get_beliefs get_blast_radius get_break_analysis get_counterfactual_summary get_credit_balance get_credit_escrow get_daily_briefing get_domain_affinity get_economy_dashboard get_feature_requests get_journal get_knowledge_gaps get_passport get_pricing get_project_context get_proof_chunks get_proof_receipt get_proof_status get_proofpack get_reasoning_profile get_session_context get_spend_receipt get_stale_pins get_trust_level get_watch_alerts get_watches github_comments_since github_open_issues github_open_prs github_recent_commits github_search invite_seat join_coalition list_projects list_seats list_work memory_engrams_resolve memory_reason_about memory_retrieve memory_session_init pin_receipt proof_document purchase_bundle query_vault query_with_threshold register_agent register_belief request_sponsor revoke_seat schedule_recheck set_policy set_reasoning_profile submit_feature_request tip_agent tip_platform unwatch_answer update_work_state verify_passport vote_feature_request watch_answer

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 & specific76/76
has a description76/76
description is substantive76/76
parameters are typed76/76
parameters are described66/7666/76

76 of 76 tools graded · 76 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
v0.3.4+sha.a5c21792df7d
server version vaultcrux-platform

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:59Zok_tools2004342025-06-18
2026-08-12T05:34:14Zok_tools2004262025-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/io.github.CueCrux/vaultcrux-platform.svg)](https://robinsaige.com/s/io.github.CueCrux/vaultcrux-platform)

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