Should my agent depend on the MCP server com.publora/mcp-server?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Publora

com.publora/mcp-server

Schedule and publish to 10 social platforms: LinkedIn, X, Instagram, TikTok, YouTube, and more.

— the operator's own registry description reported

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

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

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

Reach — can an agent get to it?

answersalive_tools

latency159 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools16

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_f6ce0dbfbec06061e7bc6258 · 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.

Tools last seen

complete_media create_post delete_media delete_post get_post get_upload_url linkedin_create_comment linkedin_create_reaction linkedin_create_reshare linkedin_delete_comment linkedin_delete_reaction linkedin_list_mentionables list_connections list_posts prune_media_reference 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 A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	16/16	✓
has a description	16/16	✓
description is substantive	14/16	14/16
parameters are typed	16/16	✓
parameters are described	16/16	✓

16 of 16 tools graded · 16 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 publora

Capabilities: tools

Drift

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

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)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:25Z	ok_tools	200	159	2025-06-18
2026-08-12T05:33:40Z	ok_tools	200	82	2025-06-18

Watch or embed this verdict

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

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