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

subframe-motion

https://mcp.subframe.com

Registry code: 054025966d442f04

api record

Use Subframe's motion library to build purposeful UI animation. Search first with search_motion_examples, then retrieve the closest suitable example with get_motion_example and adapt it using its adapt notes. If no example is close, read the relevant topics with get_motion_guidance before building motion from scratch. Animate only to explain origin, confirm input, show change, or suggest what comes next; give frequent actions little or no animation. Use 100–200 ms for hover, press and toggles; 150–250 ms for tooltips, menus and popovers; 200–350 ms for dialogs, drawers and toasts; and 300–500…

endpoint
https://mcp.subframe.com/motion/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 subframe-motion live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is subframe-motion free to use?
Yes — the hub reached it with no key and no payment.
What tools does subframe-motion have?
3 tools: get_motion_example, get_motion_guidance, search_motion_examples.
Is subframe-motion 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
179ms

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
1 open 2 never probed 1 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.

  • search_motion_examples open 1h ago

    Search the Subframe Motion Library for React animation examples. Describe what you want in plain words — the effect, the element, how it should feel, or, when matching a screenshot, what it looks like and what moves ('glowing border sweeping around a dark pricing card', 'playful press feedback for a like button', 'calm shader background behind a headline'). Results come most relevant first, with how each one looks; call get_motion_example with a slug for its code. If nothing fits closely, the result says so. Search reads plain language but not negations, so put hard constraints in the filters (runtime react means no animation library). Leave the query empty to browse a category or runtime.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 12,
          "maximum": 30,
          "minimum": 1,
          "description": "How many examples to return. Ask for more when you want variety to choose from."
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "description": "What you're looking for, in plain words. Omit to browse."
        },
        "runtime": {
          "enum": [
            "react",
            "motion",
            "webgl"
          ],
          "type": "string",
          "description": "Only return examples built this way: react needs only React, motion also needs the motion package, webgl draws with WebGL."
        },
        "category": {
          "enum": [
            "Components & interactions",
            "Animation & motion",
            "WebGL & shaders"
          ],
          "type": "string",
          "description": "Only return this category."
        }
      }
    }
    arguments 36 lines
  • get_motion_example unknown 1h ago

    Get one Subframe Motion Library example: its complete React source; how it looks and moves; adapt notes naming the code that drives the motion and what to change; the npm packages to install (none means React only); the images its code loads from /motion/assets/ with download URLs (serve them there or change the paths); reduced-motion behavior and limitations; its licence and upstream credit; related examples; the guidance topics worth reading; and a preview image. Use a slug from search_motion_examples or from a www.subframe.com/motion/<slug> URL. This writes no files: adapt the code to the project, keep its licence header, and test it there. The code targets React 19; with React 18 server rendering, move its inline <style> CSS into a stylesheet, since React 18 escapes the CSS's quotes and > characters.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "The example's slug, e.g. 'slipstream'."
        }
      }
    }
    arguments 15 lines
  • get_motion_guidance unknown 1h ago

    Get Subframe's guidance for designing motion well, by topic: principles (whether to animate at all), timing (durations, curves, springs), enter-exit (menus, dialogs, toasts), feedback (hover, press, state, loading), scroll, ambient (loops, backgrounds, shaders), text-and-numbers, performance, accessibility and adapting (turning a library example into project code). Read the relevant topics before designing, adapting or reviewing any animation, not only library examples.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "topics"
      ],
      "properties": {
        "topics": {
          "type": "array",
          "items": {
            "enum": [
              "principles",
              "timing",
              "enter-exit",
              "feedback",
              "scroll",
              "ambient",
              "text-and-numbers",
              "performance",
              "accessibility",
              "adapting"
            ],
            "type": "string"
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "The topics to read."
        }
      }
    }
    arguments 30 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 054025966d442f04.

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