Robin Saige we check the tools AI agents call

Zernio

com.zernio/zernio

Schedule, publish, and analyze social media across 15+ platforms, plus inbox, ads, and analytics.

— the operator's own registry description reported

Publisher com.zernio · first seen 2026-08-12 · endpoint https://mcp.zernio.com/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
52
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency110 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools52
vs populationhigh
capabilities6
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_f738e914e183d8759a3f8ed8 · 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 — 6 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 (6 shown, 2026-08-12 → 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-08-30outcomeok_tools (was auth_required)
2026-08-12outcomefirst probe: auth_required

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-public25serves public factstruth-checkable against a public source — the V-ladder applies in full
action24changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
retrieval-private1serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies

Tools last seen observed

account_groups_list_account_groups accounts_get accounts_get_account_health accounts_get_all_accounts_health accounts_get_follower_stats accounts_list accounts_move_account_to_profile analytics_get_analytics analytics_get_best_time_to_post analytics_get_daily_metrics analytics_get_post_timeline call_tool comments_get_inbox_post_comments comments_list_inbox_comments comments_reply_to_inbox_post docs_search media_check_upload_status media_generate_upload_link mentions_list_inbox_mentions mentions_reply_to_mention posts_bulk_upload_posts posts_create posts_cross_post posts_delete posts_edit_post posts_get posts_list posts_list_failed posts_publish_now posts_retry posts_retry_all_failed posts_unpublish_post posts_update profiles_create profiles_delete profiles_get profiles_list profiles_update queue_create_queue_slot queue_delete_queue_slot queue_get_next_queue_slot queue_list_queue_slots queue_preview_queue queue_update_queue_slot search_tools tracking_tags_get_tracking_tag_stats tracking_tags_list_tracking_tags usage_get_usage validate_media validate_post validate_post_length zernio_overview

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 & specific52/52
has a description52/52
description is substantive25/5225/52
parameters are typed52/52
parameters are described43/5243/52

52 of 52 tools graded · 52 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
3.4.4
server version Zernio

Capabilities: experimental extensions logging prompts resources 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:13:15Zok_tools2001102025-06-18
2026-08-30T06:12:55Zok_tools2001332025-06-18
2026-08-23T06:12:24Zauth_required401100
2026-08-16T06:12:12Zauth_required401107
2026-08-14T19:58:40Zauth_required401100
2026-08-12T05:33:54Zauth_required401102

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.zernio/zernio.svg)](https://robinsaige.com/s/com.zernio/zernio)

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 →