Robin Saige we check the tools AI agents call

transcription

com.scriptivox.www/transcription

AI transcription from URLs or files. 119 languages, diarization, SRT/VTT/text export.

— the operator's own registry description reported

Publisher com.scriptivox.www · first seen 2026-08-12 · endpoint https://platform.scriptivox.com/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
39
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency143 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools39
vs populationhigh
capabilities1
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_192d24b2432e25765456559c · 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-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-30 → 2026-09-06). 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 (2 events)
datetypewhat changed
2026-09-06inventorytools 37 → 39
2026-08-30outcomefirst 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-public21serves public factstruth-checkable against a public source — the V-ladder applies in full
action13changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified3not classifiable from its textTier-1 only until its tools describe themselves
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

cancel_scheduled_bot chat_with_transcript check_balance create_account create_api_key export_transcript get_account get_api_docs get_automation_run get_billing_history get_billing_portal_url get_doc get_pricing get_product_info get_supported_languages get_transcript_audio list_automations list_folders list_scheduled_meetings list_tags list_transcriptions list_workspaces move_to_folder purchase_plan revoke_api_key run_automation search_docs search_transcripts start_meeting_bot stop_meeting_bot tag_transcriptions top_up_balance transcribe_cancel transcribe_delete transcribe_status transcribe_upload transcribe_url transcription_status transcription_url

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 & specific39/39
has a description39/39
description is substantive39/39
parameters are typed39/39
parameters are described39/39

39 of 39 tools graded · 39 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
1.2.0
server version com.scriptivox.www/transcription

Capabilities: tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:12:57Zok_tools2001432025-06-18
2026-08-30T06:12:39Zok_tools2001632025-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.scriptivox.www/transcription.svg)](https://robinsaige.com/s/com.scriptivox.www/transcription)

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

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →