Robin Saige we check the tools AI agents call

SocialRobot MCP Server

io.socialrobot/socialrobot-mcp

Schedule and analyze social media posts from AI assistants. 17 tools, free on every plan.

— the operator's own registry description reported

Publisher io.socialrobot · first seen 2026-08-20 · endpoint https://socialrobot.io/api/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
19
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency465 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools19
vs populationmid
capabilities4
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_4dea56bc61c51b7bb876045d · 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 — 3 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V0 take its word ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-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 (3 shown, 2026-08-23 → 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-06outcomeok_tools (was auth_required)
2026-08-23outcomefirst 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-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
generative2creates contentno answer key exists; disclosure + stability checks, never truth verdicts
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

create_post delete_post get_account_analytics get_follower_demographics get_media_upload_url get_pinterest_top_pins get_post_analytics get_posts_with_analytics instagram_best_post_times linkedin_search_geo_locations linkedin_search_organizations linkedin_search_people_mentions list_connected_accounts list_posts pinterest_create_board pinterest_list_boards reschedule_post tiktok_get_creator_info update_post

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 & specific19/19
has a description19/19
description is substantive19/19
parameters are typed19/19
parameters are described1/191/19

19 of 19 tools graded · 19 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.0.0
server version Socialrobot.io MCP Server

Capabilities: experimental extensions 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:17:27Zok_tools2004652025-06-18
2026-08-30T06:17:14Zauth_required401484
2026-08-23T06:14:28Zauth_required401486

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

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 →