Robin Saige we check the tools AI agents call

audit

com.sulvo.publisher-revenue-audit/audit

Publisher revenue audit: ads.txt and ad-stack checks, Sulvo onboarding, and Boost ad-block recovery

— the operator's own registry description reported

Publisher com.sulvo.publisher-revenue-audit · first seen 2026-08-12 · endpoint https://publisher-revenue-audit.sulvo.com/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
37
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency167 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools37
vs populationhigh
capabilities3
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_88afc9a81b812c2013022883 · 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 B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-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
action18changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified11not classifiable from its textTier-1 only until its tools describe themselves
retrieval-public7serves public factstruth-checkable against a public source — the V-ladder applies in full
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

apply_for_sulvo_account attach_sulvo_revenue_audit connect_sulvo_backup_provider create_sulvo_ad_unit create_sulvo_auto_sticky_units create_sulvo_interstitial_units create_sulvo_signup_account delete_sulvo_ad_unit delete_sulvo_advanced_report get_publisher_monetization_benchmarks get_publisher_revenue_audit_checklist get_sulvo_activation_smoke_status get_sulvo_installation_instructions get_sulvo_report get_sulvo_revenue_onboarding_status get_sulvo_signup_ads_txt get_sulvo_signup_status import_sulvo_backup_units list_sulvo_advanced_reports lock_sulvo_placement_revision map_sulvo_placement_backup review_sulvo_placement_recommendations rollback_sulvo_activation run_publisher_revenue_audit run_sulvo_activation_preflight save_sulvo_advanced_report save_sulvo_placement_plan set_sulvo_onboarding_journey start_sulvo_revenue_onboarding start_sulvo_signup submit_sulvo_activation_workspace submit_sulvo_signup_documents submit_sulvo_site_for_approval update_sulvo_signup_company verify_sulvo_placement_installation verify_sulvo_signup_ads_txt verify_sulvo_site_ownership

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 B — usable, with rough edges.

legibility checktools passingok
name is clear & specific37/37
has a description37/37
description is substantive37/37
parameters are typed37/37
parameters are described6/376/37

37 of 37 tools graded · 37 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.3.0
server version publisher-revenue-screen

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:32Zok_tools2001672025-06-18
2026-08-12T05:33:47Zok_tools2001992025-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/com.sulvo.publisher-revenue-audit/audit.svg)](https://robinsaige.com/s/com.sulvo.publisher-revenue-audit/audit)

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