Robin Saige we check the tools AI agents call

OrbitEOS Energy Management

io.github.DeepakumarSubbian/orbiteos

Energy management platform — 61 tools for solar, battery, grid, and EV charging control

— the operator's own registry description reported

Publisher io.github.DeepakumarSubbian · first seen 2026-08-12 · endpoint https://mcp.orbiteos.cloud/sse

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
61
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency386 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools61
vs populationhigh
capabilities3
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_a54094fd9ba11713f7fd1d0f · 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?V0 take its word ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-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 (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-public30serves public factstruth-checkable against a public source — the V-ladder applies in full
action28changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-private2serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

analyze_battery_usage analyze_grid_usage assign_plugin_to_site browse_plugins check_platform_health check_system_health compare_solar_performance create_account create_component create_marketplace_category create_plugin create_role create_site create_sub_account create_user delete_component delete_role delete_site delete_sub_account delete_user describe_site describe_system execute_command export_csv get_audit_log get_channel_value get_energy_summary get_live_data get_platform_settings get_plugin_details get_site get_site_config get_system_log get_user install_plugin invite_user list_accounts list_installed_plugins list_marketplace_categories list_permissions list_roles list_site_plugins list_sites list_sub_accounts list_users query_energy_totals query_history remove_plugin_from_site search_sites set_channel_value test_smtp uninstall_plugin universal_search update_account update_component update_platform_settings update_plugin_config update_role update_site update_sub_account update_user

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 & specific61/61
has a description61/61
description is substantive57/6157/61
parameters are typed53/6153/61
parameters are described52/6152/61

61 of 61 tools graded · 61 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.1.0
server version orbiteos

Capabilities: prompts resources 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_tools2003862025-06-18
2026-08-12T05:34:14Zok_tools2003792025-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.DeepakumarSubbian/orbiteos.svg)](https://robinsaige.com/s/io.github.DeepakumarSubbian/orbiteos)

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