com.viral-cat/viral-cat

Est-ce que com.viral-cat/viral-cat est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.viral-cat/viral-cat » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 21 outils

• campaign_summary≈ 187 tokens

  Per-brand campaign rollup (brands are ViralCat's campaign unit): posted/scheduled/failed/draft counts, platforms used, next scheduled date, last posted date, and auto-post settings. Optionally scope to one brand_id.

  Paramètres, retour & exemple (2)

  Paramètres

  • brand_id · string · optionnel
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "campaign_summary", "arguments": {"brand_id": "texte", "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cancel_post≈ 267 tokens

  WRITE (safe): cancel a queued post, or move it to a new slot. Omit scheduled_date to CANCEL (status -> cancelled; the publisher ignores it). Pass scheduled_date to RESCHEDULE to that time instead (ISO 8601, at least 15 minutes out; a draft keeps its draft status). Works on draft or scheduled posts (cancel or reschedule); also works on FAILED posts but cancel-only (omit scheduled_date) — this is the way to clear a dead failed-post backlog, since failed has no other exit. Posts already posting/posted/cancelled are immutable. Get post ids from content_queue, list_posts or diagnose_failures.

  Paramètres, retour & exemple (2)

  Paramètres

  • post_id · integer · requis
    Post id to cancel or reschedule (from content_queue)
  • scheduled_date · string · optionnel
    Omit to cancel. Provide to reschedule: ISO 8601, at least 15 minutes in the future

  Exemple d'appel

  {"name": "cancel_post", "arguments": {"post_id": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• content_queue≈ 141 tokens

  The forward content pipeline: drafts awaiting approval first, then scheduled posts in publish order. Use to review what is queued before it goes out, and to find draft ids for schedule_post.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "content_queue", "arguments": {"limit": 1, "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_brand≈ 296 tokens

  WRITE (gated): create a brand (content profile) so create_draft and schedule_post have something to target. Every other write here needs a brand_id, so an agent had no way to set one up. Returns the brand_id and the Drive folder the publisher will read its media from (Viral-Cat/_Res/{name}/Vids). Publishes nothing and reaches no audience.

  Paramètres, retour & exemple (6)

  Paramètres

  • name · string · requis
    Brand name. Also names its Drive media folder, so keep it filesystem-friendly.
  • cta_url · string · optionnel
    Link included in posts.
  • hashtags · array · optionnel
    Brand hashtags appended to captions unless skip_hashtags is set.
  • description · string · optionnel
  • website_url · string · optionnel
  • content_type · string · optionnel · video | image
    What the publisher should expect to find for this brand.

  Exemple d'appel

  {"name": "create_brand", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_draft≈ 423 tokens

  WRITE (safe): create a DRAFT post for a brand. Drafts are never picked up by the publisher, so nothing goes live; a human approves in the dashboard or promotes it later with schedule_post. scheduled_date is a proposed slot (default: 7 days out).

  Paramètres, retour & exemple (6)

  Paramètres

  • caption · string · optionnel
    Post body. Omit to inherit the brand's taglines.
  • brand_id · string · requis
  • platform · string · requis
    Target platform, e.g. youtube, tiktok, instagram
  • reply_text · string · optionnel
    Follow-up reply posted under the main post. On X this is where a link belongs: a URL in the post body costs up to 94% of the reach (near-total on a non-Premium account), while the same URL one reply down costs nothing. Omit to reply with the brand's CTA url; pass an empty string for no reply at all. Ignored by every platform except X.
  • skip_hashtags · boolean · optionnel
    true = publish the caption as-is with NO brand hashtags appended; false = always append them. Omit to auto-detect: long hand-authored captions (>280 chars, no '#') skip hashtags. The result's hashtagsSkipped shows the decision.
  • scheduled_date · string · optionnel
    Proposed ISO 8601 slot, e.g. 2026-07-15T09:00:00Z

  Exemple d'appel

  {"name": "create_draft", "arguments": {"brand_id": "texte", "platform": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_media_upload≈ 435 tokens

  WRITE (gated): open a Google Drive upload session for media you hold locally, so a clip rendered on your own machine never has to be published publicly just so ViralCat can fetch it back. Returns an uploadUrl - PUT the bytes to it yourself (no auth header) and Drive stores the file; the response Location/id is the fileId for create_draft or schedule_post. When brand is given the file lands in the folder the generator actually reads for that media type: Viral-Cat/_Res/{brand}/Imgs for an image, Vids for a video, Music for audio. Without brand it defaults to the Viral-Cat folder. Video, image or audio up to 100MB. Publishes nothing and reaches no audience.

  Paramètres, retour & exemple (6)

  Paramètres

  • kind · string · optionnel · video | image | music
    Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right.
  • brand · string · optionnel
    Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given.
  • file_name · string · requis
    Name to save as in Drive, e.g. "ducktax-short.mp4".
  • folder_id · string · optionnel
    Destination Drive folder id, overriding brand.
  • mime_type · string · requis
    Media type of the file, e.g. "video/mp4".
  • size_bytes · integer · requis
    Exact byte length of the file. Drive rejects a mismatch.

  Exemple d'appel

  {"name": "create_media_upload", "arguments": {"file_name": "texte", "mime_type": "texte", "size_bytes": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• diagnose_failures≈ 205 tokens

  Group failed posts by platform + normalized failure reason: counts, date range, affected brands, a sample raw error, a recoverable flag (retry_failed_posts can re-queue it) and a concrete suggested fix per group. Answers "what is broken and why" in one call. Read-only.

  Paramètres, retour & exemple (3)

  Paramètres

  • days · integer · optionnel
    Rolling window of failed posts to analyze
  • platform · string · optionnel
    Scope to a single platform, e.g. pinterest
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "diagnose_failures", "arguments": {"days": 1, "platform": "texte", "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_brand_details≈ 210 tokens

  Full content profile for one brand: description, taglines, hashtags, CTA/website URL, niche (category/subcategory), content type, target platforms, and active discount. Use this to write on-brand captions BEFORE calling create_draft or schedule_post. Read-only; returns no secrets.

  Paramètres, retour & exemple (2)

  Paramètres

  • brand_id · string · requis
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "get_brand_details", "arguments": {"brand_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_pipeline_summary≈ 144 tokens

  High-level snapshot of the posting pipeline: active brand count, a status breakdown (how many scheduled/posted/failed/etc.), a per-platform breakdown, how many posts are due in the next 7 days, and the next scheduled date. Use for 'how's the pipeline?' style questions.

  Paramètres, retour & exemple (1)

  Paramètres

  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "get_pipeline_summary", "arguments": {"include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_brands≈ 191 tokens

  List brands (content profiles), newest first, with per-brand post counts (posted/scheduled) and the next scheduled date. Use to see which brands exist and how active each is. Excludes archived brands. Returns `total` (all active brands) next to `count` (rows returned): when `truncated` is true the roster was cut off by `limit`, so raise it (max 50) before concluding a brand does not exist.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "list_brands", "arguments": {"limit": 1, "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_connections≈ 142 tokens

  List connected platform accounts (channels) and their health: platform, account username, connected flag, posting-enabled flag, and token expiry. Use to check which platforms are wired up and whether any connection has expired. Never returns access or refresh tokens.

  Paramètres, retour & exemple (1)

  Paramètres

  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "list_connections", "arguments": {"include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_posts≈ 243 tokens

  List posts across all platforms, newest scheduled first. Each row is one publication on one platform. Filter by status (draft|scheduled|posting|posted|failed|cancelled) and/or platform (youtube|tiktok|instagram|...). Returns caption, brand name, permalink, error message when present, and publishWarning for posts that succeeded with an anomaly (e.g. published without media).

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
  • status · string · optionnel · draft | scheduled | posting | posted | failed | cancelled
  • platform · string · optionnel
    Filter to a single platform, e.g. youtube or tiktok
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "list_posts", "arguments": {"limit": 1, "status": "draft", "platform": "texte", "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• post_performance≈ 277 tokens

  Publish-outcome metrics over a rolling window (default 30 days): posted/failed/cancelled totals, success rate, per-platform breakdown, and the most recent published posts with permalinks plus their latest stored engagement snapshot (views/likes/comments/shares; available for youtube/tiktok/twitter/threads). Snapshots are stored, not live: call refresh_post_metrics first if the numbers must be current. Optionally scope by brand_id and/or platform.

  Paramètres, retour & exemple (4)

  Paramètres

  • days · integer · optionnel
  • brand_id · string · optionnel
  • platform · string · optionnel
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "post_performance", "arguments": {"days": 1, "brand_id": "texte", "platform": "texte", "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• preflight_check≈ 371 tokens

  READ-ONLY: validate a post BEFORE it is scheduled or published, so a problem is caught up front instead of discovered as a failure afterwards. Checks the exact things that produced the failed-post backlog: incompatible media for the platform (e.g. video to Pinterest), a disconnected or unrefreshable platform token (LinkedIn has no refresh token on this API tier and needs a manual browser reconnect roughly every 60 days — that's an expected state, not a bug), Facebook posting to an account with no Page (impossible via the Graph API), content referencing an already-passed date/season/promo code, and X/Twitter free-tier monthly write-cap headroom. Pass post_id to check one existing post; omit it to scan the forward queue (draft + scheduled, soonest first) and return only posts that have at least one issue.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Queue-scan mode only: how many upcoming posts to check.
  • post_id · integer · optionnel
    Check one existing post (id from list_posts or content_queue). Omit to scan the whole upcoming queue instead.
  • include_samples · boolean · optionnel
    Include sample users (email contains "sample"). Default: real data only.

  Exemple d'appel

  {"name": "preflight_check", "arguments": {"limit": 1, "post_id": 1, "include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reconnect_platform≈ 194 tokens

  WRITE (safe): attempt a server-side token refresh for a platform whose access token has lapsed, updating the stored connection's token/expiry. Works without a browser when a refresh token is on file (twitter/youtube/google_drive self-heal this way); returns needsManualReauth + a dashboard link when the platform genuinely requires a manual browser reconnect (e.g. threads). Cannot publish or touch content, only refreshes credentials; safe to retry. Never exposes tokens.

  Paramètres, retour & exemple (1)

  Paramètres

  • platform · string · requis
    Platform to reconnect, e.g. twitter, youtube, google_drive

  Exemple d'appel

  {"name": "reconnect_platform", "arguments": {"platform": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• refresh_post_metrics≈ 214 tokens

  WRITE (gated): fetch current engagement (views/likes/comments/shares) for already-published posts and store today's snapshot, then read it back with post_performance. This is the only way to update the numbers without opening the dashboard Stats tab. Supported platforms: youtube, tiktok, twitter, threads; LinkedIn and the rest expose no engagement API. A 60-minute cooldown applies per account and protects X's free-tier read quota, so a call inside it returns skipped:true and changes nothing. Publishes nothing and reaches no audience.

  Paramètres, retour & exemple (1)

  Paramètres

  • include_samples · boolean · optionnel
    Include sample users. Default false: real accounts only, matching every read tool.

  Exemple d'appel

  {"name": "refresh_post_metrics", "arguments": {"include_samples": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reschedule_post≈ 208 tokens

  WRITE (gated): move ONE post to a new future slot (ISO 8601, at least 15 minutes out). Unlike cancel_post this also accepts FAILED posts: a failed post is re-queued (status -> scheduled, error cleared). Draft and scheduled posts keep their status. Refuses posts that would structurally fail again (archived brand, incompatible media, Facebook with no Page).

  Paramètres, retour & exemple (2)

  Paramètres

  • post_id · integer · requis
    Post id (from list_posts, content_queue or diagnose_failures)
  • scheduled_date · string · requis
    New slot, ISO 8601, at least 15 minutes in the future

  Exemple d'appel

  {"name": "reschedule_post", "arguments": {"post_id": 1, "scheduled_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• retry_failed_posts≈ 384 tokens

  WRITE (gated): bulk re-queue recoverable failed posts (default reason classes: token_expired, missed_window, platform_transient_error, drive_media_missing). dry_run DEFAULTS TO TRUE and only returns the plan; pass dry_run=false to actually reschedule. Retries are staggered per platform (spacing_minutes apart) and capped at limit, so a bulk retry cannot dogpile a platform API. Posts that would structurally fail again (archived brand, incompatible media, Facebook with no Page) are skipped with the reason. Use diagnose_failures first to see what is recoverable.

  Paramètres, retour & exemple (6)

  Paramètres

  • limit · integer · optionnel
  • dry_run · boolean · optionnel
    true = plan only, change nothing (the default)
  • reasons · array · optionnel
    Failure reason classes to retry. Default: token_expired, missed_window, platform_transient_error, drive_media_missing. Non-retryable classes are rejected.
  • platform · string · optionnel
    Scope to a single platform
  • start_at · string · optionnel
    ISO 8601 start of the retry window, at least 15 minutes out. Default: ~20 minutes from now.
  • spacing_minutes · integer · optionnel
    Gap between retries on the same platform

  Exemple d'appel

  {"name": "retry_failed_posts", "arguments": {"limit": 1, "dry_run": true, "reasons": [], "platform": "texte", "start_at": "texte", "spacing_minutes": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_post≈ 446 tokens

  WRITE (gated): queue a post for FUTURE publishing, at least 15 minutes out (immediate posting is not available over MCP). Either pass post_id to promote an existing draft, or brand_id + platform to create a new scheduled post. The publishing cron sends it at the scheduled time.

  Paramètres, retour & exemple (7)

  Paramètres

  • caption · string · optionnel
  • post_id · integer · optionnel
    Draft post id to promote (from content_queue)
  • brand_id · string · optionnel
  • platform · string · optionnel
  • reply_text · string · optionnel
    Follow-up reply posted under the main post. On X this is where a link belongs: a URL in the post body costs up to 94% of the reach (near-total on a non-Premium account), while the same URL one reply down costs nothing. Omit to reply with the brand's CTA url; pass an empty string for no reply at all. Ignored by every platform except X.
  • skip_hashtags · boolean · optionnel
    true = publish the caption as-is with NO brand hashtags appended; false = always append them. Omit to auto-detect: long hand-authored captions (>280 chars, no '#') skip hashtags. When promoting a draft without a new caption, omitting this keeps the draft's existing setting.
  • scheduled_date · string · requis
    ISO 8601, at least 15 minutes in the future

  Exemple d'appel

  {"name": "schedule_post", "arguments": {"scheduled_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_brand≈ 548 tokens

  WRITE (gated): correct a brand's content profile: description, taglines, hashtags, CTA and website links, content type, and the auto-post switch. This is the repair path for a brand carrying wrong copy, which otherwise makes every caption for it wrong, and the off switch for a brand whose generator is posting against your content rules. Only the fields you pass change; the rest keep their stored values. Cannot rename a brand (the name also names its Drive media folder) and cannot touch posting frequency/day or discount settings. Queues nothing and publishes nothing itself.

  Paramètres, retour & exemple (8)

  Paramètres

  • cta_url · string · optionnel
    Link included in posts. Pass an empty string to clear it.
  • brand_id · string · requis
  • hashtags · array · optionnel
    Brand hashtags appended to captions unless skip_hashtags is set.
  • taglines · array · optionnel
    Short lines the publisher rotates through when a post has no caption of its own.
  • description · string · optionnel
    What the product actually is. The generator writes captions from this, so a wrong description makes every post wrong.
  • website_url · string · optionnel
  • content_type · string · optionnel · video | image
    What the publisher should expect to find for this brand.
  • auto_post_enabled · boolean · optionnel
    false = stop the content generator booking posts for this brand from its next cycle; true = let it resume. This is the only way to stop a brand auto-posting without opening the dashboard. Already-scheduled posts are NOT withdrawn by this: cancel those with cancel_post.

  Exemple d'appel

  {"name": "update_brand", "arguments": {"brand_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• upload_media≈ 370 tokens

  WRITE (gated): fetch a public media URL and store it in the connected Google Drive, returning the Drive fileId to pass to create_draft or schedule_post. This uploads to YOUR OWN Drive; it publishes nothing and reaches no audience. Accepts video, image or audio up to 100MB. With brand, files land in the folder the generator actually reads for that media type: Viral-Cat/_Res/{brand}/Imgs for an image, Vids for a video, Music for audio. Without brand it defaults to the Viral-Cat folder, and folder_id overrides both.

  Paramètres, retour & exemple (5)

  Paramètres

  • kind · string · optionnel · video | image | music
    Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right.
  • brand · string · optionnel
    Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given.
  • file_name · string · optionnel
    Name to save as. Omit to take it from the URL.
  • folder_id · string · optionnel
    Destination Drive folder id, overriding brand. Omit to use the Viral-Cat folder.
  • source_url · string · requis
    Public https URL of the media to store, e.g. a rendered Short. Must be reachable without auth.

  Exemple d'appel

  {"name": "upload_media", "arguments": {"source_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://viral-cat.com/api/mcp/mcp