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

lookbk

https://lookbk.dev

Registry code: 2f220828089cf2b9

api record

Lookbk (https://lookbk.dev) lists art-directed agent skills for visual work: launch films and motion video, slide decks, social images and landing pages. Use search_skills to find a skill for what the user wants to make, get_skill to read what it does, and get_install_command to get the one-line command that installs it. This server is read-only: it never installs anything itself.

endpoint
https://lookbk.dev/api/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 lookbk live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is lookbk free to use?
Yes — the hub reached it with no key and no payment.
What tools does lookbk have?
4 tools: search_skills, get_skill, get_install_command, list_video_skills.
Is lookbk 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
2,485ms

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

_ what it can do 4 tools
1 open 3 never probed 1 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.

  • list_video_skills open 49m ago

    List every Lookbk video skill (launch films, kinetic type, data stories, creator overlays, explainers). Each renders an MP4 on the user’s machine.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "free": {
          "type": "boolean",
          "description": "true for free skills only, false for Pro only."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • search_skills unknown 49m ago

    Find Lookbk agent skills for something the user wants to make, such as "product launch video", "pitch deck", "og image" or "3D hero". Returns the best matches with slug, output type, free or Pro, and page URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "free": {
          "type": "boolean",
          "description": "true for free skills only, false for Pro only."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "How many results to return (default 8)."
        },
        "query": {
          "type": "string",
          "description": "What the user wants to make, in plain words."
        },
        "output": {
          "enum": [
            "video",
            "slides",
            "image",
            "web"
          ],
          "type": "string",
          "description": "Only skills that make this kind of result."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • get_skill unknown 49m ago

    Read one Lookbk skill in full: what it makes, what it needs, what is in the package, what it is not for, an example prompt, and the command that installs it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The skill slug, e.g. \"kinetic-title-drop\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_install_command unknown never probed

    Get the one-line terminal command that installs a Lookbk skill, optionally for one agent (claude-code, codex, cursor, gemini-cli, github-copilot, opencode, vs-code) and for the user’s home folder or the current project. The server never runs it; the agent runs it in the user’s terminal.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The skill slug."
        },
        "agent": {
          "enum": [
            "claude-code",
            "codex",
            "cursor",
            "gemini-cli",
            "github-copilot",
            "opencode",
            "vs-code"
          ],
          "type": "string",
          "description": "Which agent will use it. Leave out to install for all."
        },
        "scope": {
          "enum": [
            "user",
            "project"
          ],
          "type": "string",
          "description": "\"user\" installs to the home folder (default), \"project\" into the current repository."
        }
      },
      "additionalProperties": false
    }
    arguments 34 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 2f220828089cf2b9.

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