_ registry / mcp streamable-http · checked 58m ago

vibecreator

https://vibecreator.app

Registry code: 44c14284ca573c69

api record

Tools for making short animated videos with VibeCreator. First call get_script_format, then write the script and call create_video. For explainers, use "draw" beats so the screen draws what each sentence explains. Show the returned link to the user as a markdown link, copied exactly. The video is rendered in the user's browser; nothing is stored on a server.

endpoint
https://vibecreator.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
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 vibecreator live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is vibecreator free to use?
Yes — the hub reached it with no key and no payment.
What tools does vibecreator have?
3 tools: create_video, get_script_format, list_styles.
Is vibecreator 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
100%

90 days 100%· all time 100%

latency
129ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 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_script_format open 58m ago

    Returns the full guide for writing a VibeCreator video script (one JSON object): fields, rules, places, poses, emotions, kinds of video and visual styles.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_styles open 58m ago

    Lists the visual styles a video can use (id, name, look and what it is good for).

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • create_video unknown never probed

    Checks a script written in the VibeCreator format and returns a link that opens it as an animated video in the user's browser, where they can preview it, edit every part and export the MP4. The video is built from the script by code; no image or video model is used and nothing is stored.

    mcp-tool

    {
      "type": "object",
      "required": [
        "script"
      ],
      "properties": {
        "brand": {
          "type": "string",
          "description": "Optional handle shown in the video, for example \"@mychannel\"."
        },
        "style": {
          "type": "string",
          "description": "Visual style id from list_styles (for example \"palito\" or \"jornal\"). Leave it out and the site picks one by topic."
        },
        "format": {
          "enum": [
            "9x16",
            "4x5",
            "1x1",
            "16x9"
          ],
          "type": "string",
          "description": "Frame shape. Default 9x16 (vertical)."
        },
        "script": {
          "type": "object",
          "description": "The script object described by get_script_format: { title, lang, cast, scenes: [{ place, time, mood, beats: [{ say, ... }] }], post }.",
          "additionalProperties": true
        },
        "character": {
          "enum": [
            "palito",
            "cara",
            "desenho",
            "ilustrado",
            "anime",
            "nenhum"
          ],
          "type": "string",
          "description": "How the cast is drawn: \"cara\" = white round head with an expressive face and stick limbs (the classic viral stickman look), \"palito\" = black head with big eyes, \"desenho\" = cartoon person, \"ilustrado\" = hand-drawn people, \"anime\" = 3D anime cast, \"nenhum\" = no characters. Leave it out to keep the choice the user already made on the site."
        }
      },
      "additionalProperties": false
    }
    arguments 44 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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 44c14284ca573c69.

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

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/44c14284ca573c69/badge.svg)](https://brick.blue/agent/44c14284ca573c69?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
70%

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
0

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.