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

remocn

https://remocn.dev

Registry code: f1e37b332f835baf

api record

Remocn is a shadcn registry of Remotion video components. Find components with search_components, read one with get_component before writing code against it, and use plan_video to turn a brief into a beat-by-beat storyboard. Install with `npx shadcn@latest add @remocn/<name>`. Full index: https://remocn.dev/llms-components.txt

endpoint
https://remocn.dev/mcp
protocol
http-sse ·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 remocn live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is remocn free to use?
Yes — the hub reached it with no key and no payment.
What tools does remocn have?
4 tools: get_component, search_components, plan_video, preview_component.
Is remocn 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
285ms

last good check

priced tools
0

of 4 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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_component unknown 7h ago

    Full markdown docs for one Remocn component: props, usage example, use/avoid notes and install command.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "Component name, e.g. 'kinetic-center-build'"
    }
  }
}
    arguments 14 lines
  • search_components unknown never probed

    Search Remocn Remotion components by what they do. Returns name, docs .md URL, vibe, length (frames @30fps), use/avoid notes and install command.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "vibe": {
      "enum": [
        "clean",
        "premium",
        "tech",
        "data",
        "playful",
        "social",
        "paper"
      ],
      "type": "string",
      "description": "Tonal tag to match the brand"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 500,
      "description": "What the component should do, e.g. 'typewriter headline'"
    },
    "maxLength": {
      "type": "integer",
      "maximum": 9007199254740991,
      "description": "Max motion length in frames @30fps",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 38 lines
  • plan_video unknown 7h ago

    Turn a video brief into a storyboard: picks an archetype, returns its recipe and a beat list with suggested Remocn components per beat.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "brief"
  ],
  "properties": {
    "brief": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "What the video is about, e.g. 'launch video for our CLI'"
    },
    "archetype": {
      "enum": [
        "product-demo",
        "changelog",
        "feature-announcement",
        "oss-showcase",
        "cli-tool-demo",
        "testimonial-reel",
        "year-in-review",
        "pricing-reveal",
        "logo-bumper"
      ],
      "type": "string",
      "description": "Force an archetype instead of picking by keywords"
    },
    "durationSeconds": {
      "type": "number",
      "maximum": 600,
      "description": "Target length; picks the closest recipe variant",
      "exclusiveMinimum": 0
    }
  }
}
    arguments 36 lines
  • preview_component unknown 7h ago

    Live in-chat preview of a Remocn component with optional props. Also returns its docs URL and install command.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "Component name, e.g. 'kinetic-center-build'"
    },
    "props": {
      "type": "object",
      "description": "Props merged over the component's demo defaults",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  }
}
    arguments 22 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 f1e37b332f835baf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f1e37b332f835baf/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/f1e37b332f835baf/badge.svg)](https://brick.blue/agent/f1e37b332f835baf?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
80%

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.