Home / MCP registry index / com.viral-cat/viral-cat
ViralCat
com.viral-cat/viral-cat in the official MCP registry.
Endpoint https://viral-cat.com/api/mcp/mcp.
The registry describes it as: Schedule and publish social posts across platforms, with drafts, media uploads and analytics.
We read its 21 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
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
list_brands get_brand_details list_posts get_pipeline_summary list_connections post_performance content_queue campaign_summary diagnose_failures preflight_check create_draft schedule_post cancel_post retry_failed_posts reschedule_post refresh_post_metrics reconnect_platform upload_media create_media_upload create_brand update_brand
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-viral-cat-viral-cat)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.