Should my agent depend on the MCP server com.productclank/productclank?

Verdict: allow — rich-solo — safe to depend on As of 2026-09-06T06:21:45Z: a dated observation with receipts, not a warranty.

ProductClank

com.productclank/productclank

Boost posts and launch community growth campaigns from your AI assistant. OAuth, credit-billed.

— the operator's own registry description reported

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

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a

allow — because answers ●, 36 tools legible (band A) ●, no confirmed drift in 6 probes ●; not yet checked: truth (0 runs)

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

Does it answer? Q1 · observed

answersalive_tools

latency117 ms

vs populationtypical

protocolcurrent

authopen

Can it be used? Q4 · observed

tools36

vs populationhigh

capabilities3

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_443556fe3e016e8e6d7e67e2 · 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?action ● evidence ↓

Q3Can it be checked?V n/a for this kind ◐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 (4 events)

date	type	what changed
2026-09-06	inventory	tools 30 → 36
2026-08-30	inventory	tools 8 → 30
2026-08-23	outcome	ok_tools (was http_error)
2026-08-12	outcome	first probe: http_error

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 →):

nature	tools	meaning	what checking applies
action	17	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative	10	creates content	no answer key exists; disclosure + stability checks, never truth verdicts
retrieval-public	9	serves public facts	truth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

add_delegate boost_post check_balance create_campaign create_content_campaign create_product credit_history find_open_campaigns find_opportunities generate_posts get_campaign get_campaign_activity get_campaign_brief get_campaign_results get_content_queue get_content_workspace get_earnings get_my_submissions get_posts get_research list_campaigns list_content_spaces manage_content_topics regenerate_replies review_posts revise_content_draft run_research search_products set_campaign_schedule setup_content_space submit_campaign_work submit_participation suggest_content_campaign teach_content_voice update_campaign write_content_candidates

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	36/36	✓
has a description	36/36	✓
description is substantive	36/36	✓
parameters are typed	36/36	✓
parameters are described	15/36	15/36

36 of 36 tools graded · 36 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.9.0

server version ProductClank

Capabilities: 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)	outcome	http	ms	protocol
2026-09-06T06:12:51Z	ok_tools	200	117	2025-06-18
2026-08-30T06:12:33Z	ok_tools	200	93	2025-06-18
2026-08-23T06:12:08Z	ok_tools	200	109	2025-06-18
2026-08-16T06:11:57Z	http_error	404	157
2026-08-14T19:58:25Z	http_error	404	157
2026-08-12T05:33:40Z	http_error	404	150

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

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 →