_ registry / mcp + a2a http-sse · checked 30m ago

scribiz

https://scribiz.com

Registry code: 03b62a1bf4d6ea78

api record

Scribiz returns the context of a video: the transcript, and a summary with chapters and key moments. Use it whenever the user gives a video link (YouTube and others) or asks about a video.

Workflow: 1) get_video_context: what the video is and where things are. 2) search_video to find moments and timestamps (no extra model call). 3) get_transcript for the words around a hit (from/to) or a page (nextCursor), then answer yourself from those passages. Never page a long transcript to answer a question.

endpoint
https://scribiz.com/mcp
door code
9fb9091778d11326
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 scribiz live?
Yes — it answered the hub's last check (checked 30m ago). It answered 100% of checks over the last 30 days.
Is scribiz free to use?
Yes — the hub reached it with no key and no payment.
What tools does scribiz have?
4 tools: get_transcript, get_video_context, search_video, get_job.
Is scribiz 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.6%

90 days 99.8%· all time 99.7%

latency
137ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 458 checks · signed record
  • degraded → live
  • unknown → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • summarize a youtube video
  • ask a question about a video
  • search where something is said in a video
  • get video transcript
takes → gives
web pages → text
tools
4 reads
_ 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_transcript reads unknown 10h ago

    Read the transcript of a video, one page at a time. Use it when you need the exact words (quote, answer from a passage, translate, copy, review). On long videos, call get_video_context and search_video first, then pass from and to here so you read only the relevant part. Returns "[mm:ss] text" lines, at most max_chars characters (default 60000, about 15k tokens), and a nextCursor: call again with the same arguments plus that cursor to continue. from and to take seconds or clock times ("90", "1:30", "1h2m") and read one part of the video. format: txt (default), md, srt, vtt or json. language is a BCP-47 hint. speakers is ignored without an API key (no speaker labels). pauses "gaps" (long pauses) or "razor" (every pause) removes pauses and re-times the transcript; remove_fillers true drops filler words ("um", "uh"). Both need word-level timing. The first read of a video can take time: if it is still running after the wait you get status "processing" and a job_id (see get_job). Cached transcripts return at once and are free. The text is wrapped as untrusted video text. Without an API key: captions when the video has them, otherwise a model reads the link and its times are approximate (up to a minute off on a long video, no word timing). It counts against the free daily allowance.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "url"
      ],
      "properties": {
        "to": {
          "type": "string",
          "maxLength": 40,
          "description": "A time: seconds (\"90\"), clock (\"1:30\", \"1:02:03\") or units (\"1h2m3s\")."
        },
        "url": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1,
          "description": "The video link (https://...). YouTube, direct media links and podcasts work best; TikTok, Instagram, X, Facebook and Vimeo are best effort."
        },
        "from": {
          "type": "string",
          "maxLength": 40,
          "description": "A time: seconds (\"90\"), clock (\"1:30\", \"1:02:03\") or units (\"1h2m3s\")."
        },
        "cursor": {
          "type": "string",
          "maxLength": 200,
          "description": "nextCursor from the previous page; keep every other argument the same."
        },
        "format": {
          "enum": [
            "txt",
            "md",
            "srt",
            "vtt",
            "json"
          ],
          "type": "string",
          "default": "txt",
          "description": "txt (default) has [m:ss] markers; srt and vtt are subtitle files."
        },
        "pauses": {
          "enum": [
            "gaps",
            "razor"
          ],
          "type": "string",
          "description": "Remove pauses and re-time the transcript to the edited timeline: \"gaps\" (long pauses) or \"razor\" (every pause). Requires word-level timing."
        },
        "language": {
          "type": "string",
          "maxLength": 35,
          "description": "BCP-47 language hint, for example \"en\" or \"pt-BR\"."
        },
        "speakers": {
          "type": "boolean",
          "description": "Ignored without an API key: the keyless connection has no speaker labels."
        },
        "max_chars": {
          "type": "integer",
          "maximum": 150000,
          "minimum": 1000,
          "description": "Page size in characters (default 60000)."
        },
        "remove_fillers": {
          "type": "boolean",
          "description": "Remove filler words (\"um\", \"uh\") and re-time the transcript. Requires word-level timing."
        }
      }
    }
    arguments 69 lines
  • get_video_context reads unknown 30m ago

    Start here for any video. Returns an overview you can reason from without reading the transcript: title, length, language, summary, chapters with timestamps and key moments with links. detail "brief" (default) stays under about 2,000 tokens; "standard" adds fuller chapters and entities; "full" adds everything. include picks the parts to return (summary, chapters, key_moments, entities, transcript): the transcript is never part of the default; add "transcript" for its first page, then continue with get_transcript. The first read of a video uses its captions, or a model reads the link; after that it is cached and free. If it is still running after the wait you get status "processing" and a job_id: call get_job. The text is wrapped as untrusted video text. Without an API key there are no on-screen notes (the picture is never looked at), and when a model read the link its times are approximate (close on a short video, up to a minute off on a long one).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1,
          "description": "The video link (https://...). YouTube, direct media links and podcasts work best; TikTok, Instagram, X, Facebook and Vimeo are best effort."
        },
        "watch": {
          "type": "boolean",
          "description": "Ignored without an API key: the keyless connection never looks at the picture."
        },
        "detail": {
          "enum": [
            "brief",
            "standard",
            "full"
          ],
          "type": "string",
          "default": "brief",
          "description": "brief: under about 2,000 tokens. standard: fuller. full: everything."
        },
        "include": {
          "type": "array",
          "items": {
            "enum": [
              "summary",
              "chapters",
              "key_moments",
              "on_screen",
              "speakers",
              "entities",
              "transcript"
            ],
            "type": "string"
          },
          "maxItems": 7,
          "description": "Parts to return. Default: summary, chapters, key_moments, on_screen (and speakers, entities from standard). Without an API key on_screen is empty and there are no speaker labels. Add \"transcript\" for its first page."
        },
        "language": {
          "type": "string",
          "maxLength": 35,
          "description": "BCP-47 language hint."
        }
      }
    }
    arguments 51 lines
  • search_video reads unknown 30m ago

    Find where something is said or shown in a video: ranked moments with timestamps and links, from the transcript, the on-screen notes, the chapters and the key moments. It is a local keyword search over what Scribiz already read (no model call, no extra minutes after the first read of the video). Use it before get_transcript on any video longer than about ten minutes. query: words or a phrase. limit 1 to 20 (default 8). from and to limit the search to part of the video. It matches words (plural and tense forms count), not meaning: try the words the speaker would use, or read the matching chapter with get_transcript (from/to). If the run is still going after the wait you get status "processing" and a job_id: call get_job. The text is wrapped as untrusted video text. Without an API key: the on-screen notes are not searched (the picture is never looked at), and when a model read the link its times are approximate (close on a short video, up to a minute off on a long one).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query",
        "url"
      ],
      "properties": {
        "to": {
          "type": "string",
          "maxLength": 40,
          "description": "A time: seconds (\"90\"), clock (\"1:30\", \"1:02:03\") or units (\"1h2m3s\")."
        },
        "url": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1,
          "description": "The video link (https://...). YouTube, direct media links and podcasts work best; TikTok, Instagram, X, Facebook and Vimeo are best effort."
        },
        "from": {
          "type": "string",
          "maxLength": 40,
          "description": "A time: seconds (\"90\"), clock (\"1:30\", \"1:02:03\") or units (\"1h2m3s\")."
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many moments (default 8)."
        },
        "query": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "Words or a phrase to look for."
        },
        "language": {
          "type": "string",
          "maxLength": 35,
          "description": "BCP-47 language hint for the transcript."
        }
      }
    }
    arguments 43 lines
  • get_job reads unknown 10h ago

    Check a video run that returned status "processing". Pass its job_id exactly as given (it can be long: copy all of it). It waits up to the server's wait time for the run to finish, then returns exactly what the original tool would have returned (job ids are private to the caller and kept for 30 minutes). Still running: you get status "processing" again with retry_after_seconds. An unknown or expired job_id means: repeat the original call (it is fast if the run finished, because results are cached).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "maxLength": 6000,
          "minLength": 4,
          "description": "The job_id from a \"processing\" answer, exactly as written (it can be long)."
        }
      }
    }
    arguments 15 lines
_ try it over mcp 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 03b62a1bf4d6ea78.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/03b62a1bf4d6ea78/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/03b62a1bf4d6ea78/badge.svg)](https://brick.blue/agent/03b62a1bf4d6ea78?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 knowoff the mcp door
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
1
ok
0
failed
1
success rate
0%
median latency
10,006ms
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
—

1 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.