Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ProductClank

REMOTE · MCP.PRODUCTCLANK.COM

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

0 this week 91 Trust /100

Last scanned (16 hours ago)

Scores higher than 98% of remote servers

Unreachable for 2 days in a row. Last reached 3 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 30 Oct 26 0
    • Tool “find_opportunities” rewrote its description, which is the text the model reads security
    • Tool “submit_participation” rewrote its description, which is the text the model reads security
    • New tool “hold_opportunity” functional
    • New tool “release_opportunity” functional
  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_balance” rewrote its description, which is the text the model reads security
    • Schema quality: 12569 → 13951 ▼ functional
    • Server version: 0.9.19 → 0.9.21 functional
    • New tool “set_content_bounty” functional
  • 20 Oct 26 0
    • Tool “get_growth_suggestions” rewrote its description, which is the text the model reads security
    • Tool “setup_growth_assistant” rewrote its description, which is the text the model reads security
    • Server version: 0.9.18 → 0.9.19 functional
    • “setup_growth_assistant” added an optional parameter “mix” cosmetic
  • 19 Oct 26 0
    • Tool “boost_post” rewrote its description, which is the text the model reads security
    • Tool “launch_tiktok_campaign” rewrote its description, which is the text the model reads security
    • Server version: 0.9.17 → 0.9.18 functional
    • “launch_tiktok_campaign” added an optional parameter “likes_count” cosmetic
    • “boost_post” reworded the description of “count” cosmetic
    • “launch_tiktok_campaign” reworded the description of “likes” cosmetic
    • “launch_tiktok_campaign” reworded the description of “quiz_answers” cosmetic
  • 17 Oct 26 0
    • Tool “boost_post” rewrote its description, which is the text the model reads security
    • Tool “find_open_campaigns” rewrote its description, which is the text the model reads security
    • Tool “get_campaign_brief” rewrote its description, which is the text the model reads security
    • Schema quality: 10692 → 12178 ▼ functional
    • Server version: 0.9.15 → 0.9.17 functional
    • New tool “create_watch_quiz” functional
    • New tool “get_watch_quiz_results” functional
    • New tool “launch_tiktok_campaign” functional
    • New tool “suggest_quiz_questions” functional
    • “boost_post” added an optional parameter “watch_quiz” cosmetic
  • 16 Oct 26 0
    • Tool “boost_post” rewrote its description, which is the text the model reads security
    • Tool “check_balance” rewrote its description, which is the text the model reads security
    • Tool “update_campaign” rewrote its description, which is the text the model reads security
    • Server version: 0.9.9 → 0.9.15 functional
    • New tool “get_growth_suggestions” functional
    • New tool “setup_growth_assistant” functional
    • “boost_post” added an optional parameter “count” cosmetic
    • “boost_post” added an optional parameter “post_text” cosmetic
    • “boost_post” added an optional parameter “spread_over_hours” cosmetic
    • “update_campaign” added an optional parameter “digest_enabled” cosmetic
    • “boost_post” reworded the description of “action_type” cosmetic
  • 13 Oct 26 0
    • Server version: 0.9.8 → 0.9.9 functional
    • New tool “claim_deal” functional
    • New tool “get_scout_deals” functional
    • New tool “get_scout_earnings” functional
    • New tool “rate_deal” functional
    • New tool “release_deal” functional
    • New tool “report_deal_progress” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.productclank.com/mcp

TLS unreached
DNSSEC insecure

Validation of mcp.productclank.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
productclank.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.productclank.com/mcp Unreachable
http (plaintext) http://mcp.productclank.com/mcp HTTPS enforced
MCP tools · 57 exposed · ~13,270 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
submit_campaign_work ~298

Submit the user's work for a campaign. Three ways to prove it, and any one is enough: proof_url (content they published or an action they took), media_url (a hosted image or video made for the task — the ad-hoc creative case: a demo clip, a mockup, a designed asset), and description (max 500 chars). Media must already be hosted somewhere public and reachable — this API takes links, never uploads; a direct image link is shown to the reviewer inline, anything else (a video, a Loom) is shown as a link they open. If a URL is an X post it must be published by the user's linked X handle (author-verified); other URLs are accepted as-is. Lands as PENDING — the campaign owner reviews and rewards ship on approval (community campaigns pay Stars, public ones leaderboard points). Duplicate URLs are rejected. Check status afterward with get_my_submissions.

NameTypeReqDescription
campaign_idstringyes–
descriptionstring–What was done, or context for the reviewer
media_urlstring–Public URL of an image or video produced for the task. Must already be hosted (upload it wherever the user keeps files first) — direct image links render inline for the reviewer; videos and Loom-styl…
proof_urlstring–URL of the published content or action proof (X post, video, voting page, …)

No output schema declared.

No examples provided.

submit_participation ~259

Submit the URL of what the connected user posted for an opportunity (reply_id from find_opportunities; hold it first with hold_opportunity). Submitting ends the hold. Works for X, Reddit, YouTube and LinkedIn replies, and X quote posts (actionType `quote`: pass the URL of the user's own quote post, NOT the original — the backend checks it was posted by their linked X handle and that it actually quotes the target post; a plain tweet or a quote of something else is rejected). Every claim is attributed to the user's linked handle for that platform, so they must have it connected on their ProductClank profile — X replies are additionally author-verified against the live post at submit time, and the others are verified afterwards by the same checks that cover web submissions. If the platform handle is missing the call fails saying which one to add. Awards points, and credits when the campaign grants them. Rejected submissions add strikes (3 strikes = blocked), so only submit replies the user actually posted.

NameTypeReqDescription
reply_idstringyesThe reply draft's id from find_opportunities
reply_urlstringyesURL of the reply (or, for a quote opportunity, the quote post) the user posted

No output schema declared.

No examples provided.

suggest_content_campaign ~251

Preview a content campaign for a product BEFORE launching it. FREE — nothing is created and no credits are charged. Returns an AI-drafted campaign (title, description, call-to-action) plus whether the user can afford to launch it (1000 credits). Show the user the draft AND the credit cost, get an explicit yes, then call create_content_campaign — never launch off the back of the preview alone. Requires a product_id from search_products; write the campaign_message brief from what you know about the product.

NameTypeReqDescription
additional_guidelinesstring–Extra do's/don'ts for creators
campaign_goalsarray–Campaign goals, e.g. ["awareness", "signups"]
campaign_messagestringyesThe core brief: what you want the community to create (e.g. 'Share how you use <product> in your daily workflow').
preferred_platformstring–Preferred platform, e.g. "x" or "farcaster"
product_idstringyesProduct UUID from search_products
referencesstring–Links or references to include in the campaign
target_audiencestring–Who the campaign should reach

No output schema declared.

No examples provided.

suggest_quiz_questions ~109

AI watches a TikTok (frames + captions) and suggests counting questions with their answers and the evidence for each — high confidence only. Creates nothing. Costs 40 credits, charged only when questions come back. Show every question WITH its evidence to the user and pass only the ones they confirm to create_watch_quiz (or boost_post's watch_quiz). If it fails, nothing is charged — ask the user for questions instead.

NameTypeReqDescription
video_urlstringyesTikTok video URL.

No output schema declared.

No examples provided.

teach_content_voice ~200

Teach the engine. The user's reaction — 'too long', 'punchier hooks', 'never say leverage', 'more first-person on LinkedIn' — becomes a durable rule in the brand's voice KB, so every future draft and review honors it. 1 credit. Use it when feedback should STICK; use revise_content_draft when it is about one draft only. Pass draft_id when the reaction was to a specific draft so the rule is grounded in an example. The rule is applied immediately by default (the user owns the space); apply:false leaves it pending in the web Settings instead. Tell the user in one line what was learned.

NameTypeReqDescription
applyboolean–Default true. false → leave pending for the user to approve in Settings.
draft_idstring–The draft it was about, if any.
feedbackstringyesThe user's reaction, in their words.
space_idstringyes–

No output schema declared.

No examples provided.

update_campaign ~1,016

Adjust a live campaign without recreating it. Free — nothing here spends credits, though the next generate_posts run bills as usual. Keywords MERGE (add_keywords never drops what is already there). `sources` is how research findings get applied: high-intent phrases, influencer accounts and lists that run_research found stay dormant until you enable their source. `relevance_threshold` moves the bar the relevance gate keeps posts above (new campaigns start lenient at 5; raise it when discovery is noisy). `is_active:false` pauses discovery so nothing more is found or billed. `digest_enabled:true` emails the owner and the campaign's delegates once a day with the new posts and their draft replies, so they can reply without opening the app; offer it when the user will post the replies themselves (a private campaign). `visibility` decides who posts the drafts — flipping to 'public' also releases the already-discovered drafts to the community, so only do it when the user has said yes. `target_subreddits` / `target_youtube_channels` re-aim discovery within its platform (send an empty array to clear and search the whole platform). `platform` itself can only change while the campaign has discovered nothing — after that it is fixed, and a second campaign is the answer. On X, `reply_approach` switches what the replies do (awareness 'mention' vs sales 'flag', which tags reply_tag_accounts at the lead) — confirm with the user, it changes every future draft. Changes apply to the NEXT generate_posts run; existing posts are not re-scored.

NameTypeReqDescription
add_keywordsarray–Keywords to add — merged with the existing list, duplicates ignored
campaign_idstringyes–
confirmboolean–Required (true) when setting visibility to public — confirms the user agreed to community distribution and per-posted-reply billing. Without it the API returns confirmation_required.
digest_enabledboolean–true = once a day, email the owner and every delegate (add_delegate) the posts found since the last digest, each with its draft reply and a link to reply. Only sent on days with new posts; each recip…
is_activeboolean–false pauses discovery, true resumes it
monitor_accountsarray–Specific handles the influencers source should watch; enables that source automatically
platformstring–Which network discovery works. Only changeable while the campaign has discovered nothing — otherwise it returns platform_locked, because switching would mix two platforms' posts and proof rules in on…
post_visibilitystring–Visibility of posts discovered FROM NOW ON, without touching the campaign flag or existing posts. 'private' turns on held mode (release with publish_posts); 'public' makes new drafts claimable on arr…
relevance_thresholdinteger–Keep only posts scoring at or above this on semantic relevance (new campaigns start at 5)
remove_keywordsarray–Keywords to drop (at least one must remain)
reply_approachstring–X campaigns only (REJECTED elsewhere). 'mention' = awareness: replies put the product and its site in the conversation. 'flag' = sales: replies tag the brand and/or founder at the post's author as a…
reply_tag_accounts––X only, for 'flag': up to 2 handles to tag, brand first then founder (brand, personal or both). REPLACES the list; null or [] clears it (falls back to mention_accounts, then the product's X handle).
sourcesarray–Which discovery sources run. 'keywords' is always included. Enable 'phrases'/'influencers'/'lists'/'competitors' to actually USE what run_research found — they do nothing until enabled.
target_subredditsarray–Reddit only, enforced server-side — sending it on a non-Reddit campaign is REJECTED, not ignored. REPLACES the list rather than appending; [] clears it and searches all of Reddit. To add one, read th…
target_youtube_channelsarray–YouTube only, enforced server-side — sending it on a non-YouTube campaign is REJECTED, not ignored. REPLACES the list rather than appending; [] clears it and runs keyword search alone. To add one, re…
visibilitystring–Who posts the drafted replies. private = the user posts them from the workbench; public = the community earn feed distributes them and members post them, billing the user per posted reply. Flipping t…

No output schema declared.

No examples provided.

write_content_candidates ~168

Draft one or more posts into a ProductClank content space. FREE. Call get_content_workspace FIRST and write in that brand's voice, post types and topics — the drafts are scored against exactly that voice by the reviewer a moment after they land, and the scores show in get_content_queue. `platform` must be one of the space's platforms (omit it to use the first). Candidates land in the user's 'All Content' queue for approval; nothing is auto-published. Up to 25 per call. This drafts into the user's OWN content pipeline — it is NOT a community content campaign (use create_content_campaign for that).

NameTypeReqDescription
candidatesarrayyes1–25 draft candidates to write.
space_idstringyesTarget content space UUID from list_content_spaces.

No output schema declared.

No examples provided.

Install

How do I install the ProductClank MCP server?

ProductClank is a hosted endpoint at https://mcp.productclank.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.productclank.com

# add to Claude Code
claude mcp add --transport http com-productclank-productclank 'https://mcp.productclank.com/mcp'
Common questions

What is the ProductClank MCP server?

ProductClank is an MCP server listed in the public MCP registry as com.productclank/productclank. Boost posts and launch community growth campaigns from your AI assistant. OAuth, credit-billed. This page covers its hosted endpoint (https://mcp.productclank.com/mcp).

Is the ProductClank MCP server safe to use?

ProductClank scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ProductClank MCP server expose?

ProductClank exposes 57 tools: search_products, create_product, check_balance, credit_history, boost_post, and 52 more. Their descriptions and schemas cost roughly 13,270 tokens of context every time the server is loaded.

Does the ProductClank MCP server require authentication?

Its publisher declares no required credentials for ProductClank. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the ProductClank MCP server still maintained?

ProductClank is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ProductClank MCP server?

VerifyMCP ran 3 checks on ProductClank, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about ProductClank: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.