Robin Saige we check the tools AI agents call

upgrade agent

ai.upgradeagent/upgrade-agent

Travel-upgrade Q&A, live booking eligibility, and operator lookups for airline, cruise, rail.

— the operator's own registry description reported

Publisher ai.upgradeagent · first seen 2026-08-12 · endpoint https://www.upgradeagent.ai/api/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
17
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency199 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools17
vs populationmid
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_518d8213439b011b32317c2b · 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?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 (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-public10serves public factstruth-checkable against a public source — the V-ladder applies in full
action6changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

ask_upgrade_agent check_upgrade_eligibility get_bid_status get_eligibility_result get_partner_info get_upgrade_pricing get_watch_status list_partners mint_eligibility_session modify_bid partner_question_insights place_bid predict_bid_success search_upgrade_options start_eligibility_check start_watch usage_totals

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 & specific17/17
has a description17/17
description is substantive17/17
parameters are typed17/17
parameters are described14/1714/17

17 of 17 tools graded · 17 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 yet confirmed — 3 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts
tariff-duty8471.30.01unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version upgrade-agent

Capabilities: 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:57:43Zok_tools2001992025-06-18
2026-08-12T05:33:00Zok_tools2003002025-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/ai.upgradeagent/upgrade-agent.svg)](https://robinsaige.com/s/ai.upgradeagent/upgrade-agent)

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