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

vozclara

https://vozclara.app

Registry code: 563f12272285a187

api record

Turn any public video URL into a structured Knowledge Pack — summary, key ideas, glossary, quiz, transcript with timestamps — in Spanish, Portuguese, German, or English.

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

endpoint
https://vozclara.app/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,051ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 1 tools
1 never probed 0 of 1 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.

  • vozclara_generate_pack unknown never probed

    Use this when the user asks for a summary, key ideas, or study material from a YouTube video. Returns a structured Knowledge Pack: title, short summary, key ideas, and a link to the full pack on vozclara.app. Pass format="obsidian" to get vault-ready Markdown with YAML frontmatter the user can save to their second brain.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url",
        "language"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "Public YouTube video URL (youtube.com/watch?v=… or youtu.be/… short form)."
        },
        "depth": {
          "enum": [
            "short",
            "standard",
            "deep"
          ],
          "type": "string",
          "default": "standard",
          "description": "Depth of the generated pack. `short` = one-paragraph summary. `standard` = summary + 3-5 key ideas. `deep` = summary + key ideas + glossary + quiz."
        },
        "format": {
          "enum": [
            "standard",
            "obsidian"
          ],
          "type": "string",
          "default": "standard",
          "description": "Output format. `standard` = plain prose for chat. `obsidian` = Markdown with YAML frontmatter (source, videoId, languages, tags) ready to write straight into an Obsidian vault or any Markdown knowledge base. Use `obsidian` when the user asks to save the pack to their vault / second brain / notes."
        },
        "language": {
          "enum": [
            "es",
            "pt",
            "de",
            "en"
          ],
          "type": "string",
          "description": "Output language for the Knowledge Pack: es (Spanish), pt (Portuguese), de (German), en (English)."
        }
      }
    }
    arguments 44 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/563f12272285a187/badge.svg)](https://brick.blue/agent/563f12272285a187)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
50%

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.