Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is viral-cat free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does viral-cat have?

21 tools: get_brand_details, create_draft, retry_failed_posts, create_brand, post_performance, refresh_post_metrics, content_queue, list_connections, ….

Is viral-cat safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 1h ago

viral-cat

https://viral-cat.com

Registry code: 0dac75cf51a3a991

api record

Schedule and publish social posts across platforms, with drafts, media uploads and analytics.

from a public catalogue that lists it, not from the operator

endpoint: https://viral-cat.com/api/mcp/mcp
protocol: http-sse ·2025-06-18
authentication: bearer
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is viral-cat live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is viral-cat free to use?: Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does viral-cat have?: 21 tools: get_brand_details, create_draft, retry_failed_posts, create_brand, post_performance, refresh_post_metrics, content_queue, list_connections, ….
Is viral-cat safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.6%

90 days 99.7%· all time 99.7%

latency

267ms

last good check

priced tools

of 21 tools

_ answered our checks, 90 days 358 checks · signed record

2026-11-02 03:42 degraded → live
2026-11-02 01:29 live → degraded· timeout after 20000ms
2026-10-12 10:02 degraded → live
2026-09-26 19:42 unknown → live

_ what it is for

topic: communication social media
used for: schedule social media posts
create post drafts
diagnose failed posts
get post performance metrics
takes → gives: text, images, video → data
tools: 10 reads11 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 21 tools

21 auth-required 21 of 21 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_brand_details reads auth-required 4h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "brand_id"
  ],
  "properties": {
    "brand_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "include_samples": {
      "type": "boolean",
      "default": false,
      "description": "Include sample users (email contains \"sample\"). Default: real data only."
    }
  }
}

arguments 19 lines

create_draft changes data auth-required never probed

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).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "brand_id",
    "platform"
  ],
  "properties": {
    "caption": {
      "type": "string",
      "maxLength": 2200,
      "description": "Post body. Omit to inherit the brand's taglines."
    },
    "brand_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "platform": {
      "type": "string",
      "maxLength": 20,
      "description": "Target platform, e.g. youtube, tiktok, instagram"
    },
    "reply_text": {
      "type": "string",
      "maxLength": 2200,
      "description": "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": {
      "type": "boolean",
      "description": "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": {
      "type": "string",
      "description": "Proposed ISO 8601 slot, e.g. 2026-07-15T09:00:00Z"
    }
  }
}

arguments 38 lines

retry_failed_posts changes data auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "dry_run": {
      "type": "boolean",
      "default": true,
      "description": "true = plan only, change nothing (the default)"
    },
    "reasons": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40
      },
      "description": "Failure reason classes to retry. Default: token_expired, missed_window, platform_transient_error, drive_media_missing. Non-retryable classes are rejected."
    },
    "platform": {
      "type": "string",
      "maxLength": 20,
      "description": "Scope to a single platform"
    },
    "start_at": {
      "type": "string",
      "description": "ISO 8601 start of the retry window, at least 15 minutes out. Default: ~20 minutes from now."
    },
    "spacing_minutes": {
      "type": "integer",
      "default": 30,
      "maximum": 240,
      "minimum": 5,
      "description": "Gap between retries on the same platform"
    }
  }
}

arguments 41 lines

create_brand changes data auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Brand name. Also names its Drive media folder, so keep it filesystem-friendly."
    },
    "cta_url": {
      "type": "string",
      "maxLength": 500,
      "description": "Link included in posts."
    },
    "hashtags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100
      },
      "maxItems": 30,
      "description": "Brand hashtags appended to captions unless skip_hashtags is set."
    },
    "description": {
      "type": "string",
      "maxLength": 1000
    },
    "website_url": {
      "type": "string",
      "maxLength": 500
    },
    "content_type": {
      "enum": [
        "video",
        "image"
      ],
      "type": "string",
      "description": "What the publisher should expect to find for this brand."
    }
  }
}

arguments 45 lines

post_performance reads auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "days": {
      "type": "integer",
      "default": 30,
      "maximum": 365,
      "minimum": 1
    },
    "brand_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "platform": {
      "type": "string",
      "maxLength": 20
    },
    "include_samples": {
      "type": "boolean",
      "default": false,
      "description": "Include sample users (email contains \"sample\"). Default: real data only."
    }
  }
}

arguments 26 lines

refresh_post_metrics changes data auth-required never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "include_samples": { "type": "boolean", "default": false, "description": "Include sample users. Default false: real accounts only, matching every read tool." } } }
arguments 11 lines

content_queue reads auth-required 8h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 100,
      "minimum": 1
    },
    "include_samples": {
      "type": "boolean",
      "default": false,
      "description": "Include sample users (email contains \"sample\"). Default: real data only."
    }
  }
}

arguments 17 lines

list_connections reads auth-required 4h ago
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "include_samples": { "type": "boolean", "default": false, "description": "Include sample users (email contains \"sample\"). Default: real data only." } } }
arguments 11 lines
list_brands reads auth-required 12h ago
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1 }, "include_samples": { "type": "boolean", "default": false, "description": "Include sample users (email contains \"sample\"). Default: real data only." } } }
arguments 17 lines

list_posts reads auth-required never probed

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "status": {
      "enum": [
        "draft",
        "scheduled",
        "posting",
        "posted",
        "failed",
        "cancelled"
      ],
      "type": "string"
    },
    "platform": {
      "type": "string",
      "maxLength": 20,
      "description": "Filter to a single platform, e.g. youtube or tiktok"
    },
    "include_samples": {
      "type": "boolean",
      "default": false,
      "description": "Include sample users (email contains \"sample\"). Default: real data only."
    }
  }
}

arguments 33 lines

get_pipeline_summary reads auth-required 12h ago
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "include_samples": { "type": "boolean", "default": false, "description": "Include sample users (email contains \"sample\"). Default: real data only." } } }
arguments 11 lines

campaign_summary reads auth-required 8h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "brand_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "include_samples": {
      "type": "boolean",
      "default": false,
      "description": "Include sample users (email contains \"sample\"). Default: real data only."
    }
  }
}

arguments 16 lines

diagnose_failures reads auth-required 8h ago

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "days": {
      "type": "integer",
      "default": 60,
      "maximum": 365,
      "minimum": 1,
      "description": "Rolling window of failed posts to analyze"
    },
    "platform": {
      "type": "string",
      "maxLength": 20,
      "description": "Scope to a single platform, e.g. pinterest"
    },
    "include_samples": {
      "type": "boolean",
      "default": false,
      "description": "Include sample users (email contains \"sample\"). Default: real data only."
    }
  }
}

arguments 23 lines

preflight_check reads auth-required 12h ago
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1, "description": "Queue-scan mode only: how many upcoming posts to check." }, "post_id": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "Check one existing post (id from list_posts or content_queue). Omit to scan the whole upcoming queue instead." }, "include_samples": { "type": "boolean", "default": false, "description": "Include sample users (email contains \"sample\"). Default: real data only." } } }
arguments 24 lines

schedule_post changes data auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scheduled_date"
  ],
  "properties": {
    "caption": {
      "type": "string",
      "maxLength": 2200
    },
    "post_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Draft post id to promote (from content_queue)"
    },
    "brand_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "platform": {
      "type": "string",
      "maxLength": 20
    },
    "reply_text": {
      "type": "string",
      "maxLength": 2200,
      "description": "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": {
      "type": "boolean",
      "description": "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": {
      "type": "string",
      "description": "ISO 8601, at least 15 minutes in the future"
    }
  }
}

arguments 41 lines

cancel_post changes data auth-required never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "post_id" ], "properties": { "post_id": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "Post id to cancel or reschedule (from content_queue)" }, "scheduled_date": { "type": "string", "description": "Omit to cancel. Provide to reschedule: ISO 8601, at least 15 minutes in the future" } } }
arguments 19 lines

reschedule_post changes data auth-required never probed

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).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "post_id",
    "scheduled_date"
  ],
  "properties": {
    "post_id": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Post id (from list_posts, content_queue or diagnose_failures)"
    },
    "scheduled_date": {
      "type": "string",
      "description": "New slot, ISO 8601, at least 15 minutes in the future"
    }
  }
}

arguments 20 lines

reconnect_platform changes data auth-required never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "platform" ], "properties": { "platform": { "type": "string", "maxLength": 20, "description": "Platform to reconnect, e.g. twitter, youtube, google_drive" } } }
arguments 14 lines

upload_media changes data auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "source_url"
  ],
  "properties": {
    "kind": {
      "enum": [
        "video",
        "image",
        "music"
      ],
      "type": "string",
      "description": "Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right."
    },
    "brand": {
      "type": "string",
      "maxLength": 200,
      "description": "Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given."
    },
    "file_name": {
      "type": "string",
      "maxLength": 200,
      "description": "Name to save as. Omit to take it from the URL."
    },
    "folder_id": {
      "type": "string",
      "maxLength": 200,
      "description": "Destination Drive folder id, overriding brand. Omit to use the Viral-Cat folder."
    },
    "source_url": {
      "type": "string",
      "format": "uri",
      "description": "Public https URL of the media to store, e.g. a rendered Short. Must be reachable without auth."
    }
  }
}

arguments 38 lines

create_media_upload changes data auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "file_name",
    "mime_type",
    "size_bytes"
  ],
  "properties": {
    "kind": {
      "enum": [
        "video",
        "image",
        "music"
      ],
      "type": "string",
      "description": "Which brand folder receives the file: Vids, Imgs or Music. Omit to route by media type, which is almost always right."
    },
    "brand": {
      "type": "string",
      "maxLength": 200,
      "description": "Brand whose _Res/{brand} folder should receive the file. Ignored when folder_id is given."
    },
    "file_name": {
      "type": "string",
      "maxLength": 200,
      "description": "Name to save as in Drive, e.g. \"ducktax-short.mp4\"."
    },
    "folder_id": {
      "type": "string",
      "maxLength": 200,
      "description": "Destination Drive folder id, overriding brand."
    },
    "mime_type": {
      "type": "string",
      "maxLength": 100,
      "description": "Media type of the file, e.g. \"video/mp4\"."
    },
    "size_bytes": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Exact byte length of the file. Drive rejects a mismatch.",
      "exclusiveMinimum": 0
    }
  }
}

arguments 46 lines

update_brand changes data auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "brand_id"
  ],
  "properties": {
    "cta_url": {
      "type": "string",
      "maxLength": 500,
      "description": "Link included in posts. Pass an empty string to clear it."
    },
    "brand_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "hashtags": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100
      },
      "maxItems": 30,
      "description": "Brand hashtags appended to captions unless skip_hashtags is set."
    },
    "taglines": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 500
      },
      "maxItems": 30,
      "description": "Short lines the publisher rotates through when a post has no caption of its own."
    },
    "description": {
      "type": "string",
      "maxLength": 1000,
      "description": "What the product actually is. The generator writes captions from this, so a wrong description makes every post wrong."
    },
    "website_url": {
      "type": "string",
      "maxLength": 500
    },
    "content_type": {
      "enum": [
        "video",
        "image"
      ],
      "type": "string",
      "description": "What the publisher should expect to find for this brand."
    },
    "auto_post_enabled": {
      "type": "boolean",
      "description": "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."
    }
  }
}

arguments 58 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0dac75cf51a3a991.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0dac75cf51a3a991/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/0dac75cf51a3a991/badge.svg)](https://brick.blue/agent/0dac75cf51a3a991?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.