Home / MCP registry index / com.productclank/productclank

ProductClank

com.productclank/productclank in the official MCP registry. Endpoint https://mcp.productclank.com/mcp. Source: github.com/covariance-network/productclank-mcp-server.

The registry describes it as: Boost posts and launch community growth campaigns from your AI assistant. OAuth, credit-billed.

We read its 55 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

search_products create_product check_balance credit_history boost_post create_watch_quiz suggest_quiz_questions get_watch_quiz_results launch_tiktok_campaign suggest_content_campaign create_content_campaign set_content_bounty get_content_campaign_results list_content_spaces write_content_candidates get_content_workspace setup_content_space manage_content_topics get_content_queue revise_content_draft teach_content_voice analyze_url create_campaign list_campaigns get_campaign run_research get_research generate_posts get_posts review_posts regenerate_replies get_campaign_activity get_campaign_results update_campaign set_campaign_schedule add_delegate edit_reply publish_posts find_opportunities submit_participation find_open_campaigns get_campaign_brief submit_campaign_work get_my_submissions get_earnings get_scout_deals claim_deal release_deal report_deal_progress rate_deal get_scout_earnings setup_growth_assistant get_growth_suggestions report_issue get_support_status

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-productclank-productclank/badge.svg)](https://lazaretto.dev/mcp-registry/com-productclank-productclank)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.