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

keptbits

https://keptbits.com

Registry code: 72eff1db2bb8a1d1

api record

Keptbits turns long videos into short vertical clips with captions burned in.

How it is priced, which is the thing most often got wrong: one token is one clip. It is NOT minutes of footage, not video length, and not a per-minute rate. A three-hour episode and a ten-minute one cost the same for the same number of clips. The user chooses how many clips a run makes and pays one token for each. Never tell the user their balance is in minutes or that it depends on how long their video is.

endpoint
https://keptbits.com/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 keptbits live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is keptbits free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does keptbits have?
5 tools: list_clips, create_clips, list_sources, check_job, get_account.
Is keptbits 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
99.7%

90 days 99.8%· all time 99.8%

latency
292ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 416 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
media generation video
used for
  • turn a long video into short clips
  • check a clip job progress
  • list uploaded video sources
  • check account plan limits
takes → gives
video, web pages → video, data
tools
4 reads1 changes data
_ 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 5 tools
5 auth-required 5 of 5 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_clips reads auth-required 17h ago

    Clips made on this account recently, newest first.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "1 to 25, default 10"
    }
  }
}
    arguments 9 lines
  • create_clips changes data auth-required never probed

    Start finding and rendering short vertical clips from a video. Give either source_id (from list_sources) or youtube_url. This costs one token per clip, so ask the user how many they want if they have not said, and set clip_count to that number. It returns a job_id immediately — rendering takes several minutes — then poll check_job.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "aspect": {
      "enum": [
        "9:16",
        "1:1",
        "16:9"
      ],
      "type": "string",
      "description": "Default 9:16"
    },
    "source_id": {
      "type": "string",
      "description": "A source already on the account"
    },
    "clip_count": {
      "type": "number",
      "description": "How many clips to make, 1 to 100. One token each, and the user chooses freely — if the balance will not cover the number you first tried, call this again with a smaller one rather than reporting that the run cannot be made. Default 5"
    },
    "window_end": {
      "type": "number",
      "description": "Read until this second. 0 means the end"
    },
    "youtube_url": {
      "type": "string",
      "description": "Link to a single YouTube video"
    },
    "window_start": {
      "type": "number",
      "description": "Read from this second of the source"
    },
    "caption_style": {
      "type": "string",
      "description": "Caption preset name. Default bold"
    },
    "target_length": {
      "type": "number",
      "description": "Seconds per clip, 15 to 180. Default 30"
    }
  }
}
    arguments 42 lines
  • list_sources reads auth-required 17h ago

    Videos already uploaded or linked on this account, newest first. Use it to find the source_id for making clips.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "1 to 25, default 10"
    }
  }
}
    arguments 9 lines
  • check_job reads auth-required 24h ago

    Progress of a clip run, and the finished clips once it is done.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • get_account reads auth-required 17h ago

    The signed-in Keptbits account: its plan and what that plan allows. Check this before starting a run, so the run asks for something the account can actually have.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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 72eff1db2bb8a1d1.

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

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.