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

kavel

https://www.kavel.ai

Registry code: 762184c8b30b696d

api record

Discover Kavel's AI photo/video generators, get tuned prompts, and open the right tool on kavel.ai.

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

endpoint
https://www.kavel.ai/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 kavel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is kavel free to use?
Yes — the hub reached it with no key and no payment.
What tools does kavel have?
4 tools: generate_kavel_image, get_kavel_balance, check_kavel_generation, find_kavel_tool.
Is kavel 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
347ms

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.

  • find_kavel_tool open 1h ago

    Search Kavel's AI photo and video effects (hairstyle changer, figurine, pet portrait, yearbook photo, trend dance videos and more). Returns each tool's slug, what it needs (a photo or just text) and its page on kavel.ai. Image tools can be run here with generate_kavel_image; video tools open on kavel.ai.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "hub": {
          "enum": [
            "image",
            "video"
          ],
          "type": "string",
          "description": "Only image or only video tools."
        },
        "query": {
          "type": "string",
          "description": "What the user wants, e.g. 'make my dog look royal' or 'dancing video'."
        }
      }
    }
    arguments 18 lines
  • generate_kavel_image unknown never probed

    Create an image from a prompt, or edit the user's photo, on their Kavel account. Pass `tool` (a slug from find_kavel_tool) to apply that effect's tuned recipe, with `prompt` holding the user's own details. Photo tools need a photo: the user's attachment in `photos`, or a public link in `image_urls`. Spends credits from the linked Kavel account. Usually returns the image within a minute; otherwise returns a task_id for check_kavel_generation.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tool": {
          "type": "string",
          "description": "Optional image tool slug from find_kavel_tool."
        },
        "photos": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "download_url",
              "file_id"
            ],
            "properties": {
              "file_id": {
                "type": "string"
              },
              "file_name": {
                "type": "string"
              },
              "mime_type": {
                "type": "string"
              },
              "download_url": {
                "type": "string",
                "format": "uri"
              }
            }
          },
          "maxItems": 4,
          "description": "Photos the user attached in the chat. Required by photo tools."
        },
        "prompt": {
          "type": "string",
          "maxLength": 2000,
          "description": "The user's description, or their extra details when a tool is given."
        },
        "image_urls": {
          "type": "array",
          "items": {
            "type": "string",
            "format": "uri"
          },
          "maxItems": 4,
          "description": "Photos to edit given as public http(s) links, when not attached."
        },
        "aspect_ratio": {
          "enum": [
            "1:1",
            "16:9",
            "9:16",
            "4:3",
            "3:4"
          ],
          "type": "string"
        }
      }
    }
    arguments 61 lines
  • get_kavel_balance unknown 1h ago

    How many credits are left on the linked Kavel account.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • check_kavel_generation unknown 1h ago

    Get the result of a Kavel generation that was still rendering.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "task_id"
      ],
      "properties": {
        "task_id": {
          "type": "string",
          "description": "task_id from generate_kavel_image."
        }
      }
    }
    arguments 13 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 762184c8b30b696d.

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