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

Yank

listed under this name in a public catalogue; the server gives only its address, yank.info

https://yank.info

Registry code: 2b4addd21303802f

api record

yank.info extracts the five most quotable lines from a podcast, video, essay, article or PDF and gives each a permanent card URL. Use search_lines to find lines, get_yank to read one yank with full provenance, get_lines_for_url to ask what the library already holds from a source, check_quote to check whether a statement is in the source it is attributed to (a verdict and a receipt, never a judgement on whether the statement is true), and check_memory to put a batch of remembered claims through that same check at once, which is what to reach for when you are auditing notes you or another agent…

endpoint
https://yank.info/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 Yank live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Yank free to use?
Yes — the hub reached it with no key and no payment.
What tools does Yank have?
7 tools: get_lines_for_url, check_quote, search_transcripts, get_yank, check_memory, search_lines, recent_yanks.
Is Yank 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.8%

90 days 99.8%· all time 99.8%

latency
443ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 562 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • extract quotable lines from a source
  • search extracted quotes
  • check if a quote appears in its source
  • list lines held for a url
takes → gives
text, web pages → text, data
tools
5 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

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

  • recent_yanks reads open 16h ago

    The newest yanks in the library, one card each (rank-1 line, author, source type, URL).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 24,
          "minimum": 1
        }
      }
    }
    arguments 11 lines
  • get_lines_for_url reads unknown 5h ago

    Ask before you extract: everything yank.info already holds from one source URL. Any form of the link works (a youtu.be short link with a timestamp, a watch URL with a playlist, an article with tracking parameters, an Apple Podcasts or Overcast episode link); equivalent URLs return the same answer. Returns real counts (yanks, lines, verbatim lines) and, for up to five yanks, every line with its verbatim flag, timestamp, moment link, context and permanent card URL. Zero yanks is an answer, not an error. Reads the library only; never fetches the source.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The source URL in any of its forms."
        }
      }
    }
    arguments 12 lines
  • check_quote reads unknown 12h ago

    Yank Check: a statement and the source it is supposed to come from, in; a verdict and a receipt, out. FOUND (the words are in the representation Yank inspected), CLOSE MATCH (substantially the same wording, with the difference shown), DISTILLED MATCH (a passage shares most of the statement's content words but not its literal words; shared words can say the opposite, so read the passage), NOT FOUND (Yank inspected an adequate representation and could not find support), or CAN'T ESTABLISH (Yank could not obtain or inspect enough evidence; the reason says why). With where (a moment for media, the publisher's page opened on the exact words for an article), speaker with the class of that claim (file-stated, representation-stated, not-established), the passage around it, which representation was read (captions, transcript, article text, filing, document) and how much of it (inspected: words, duration), and when. A NOT FOUND is a bounded claim scoped to the representation read, never a claim that the words were not said; a CLOSE MATCH lists the words that differ (difference.tokens), never a similarity number; every verdict carries one plain sentence (finding). No model is consulted: the verdict resolves against the representation itself. Sources Yank already holds check immediately; an article, a public PDF (located by page) or a captioned video is read for the check; audio that would need transcribing is not spent on here and returns CAN'T ESTABLISH with acquisition_required, so yank it first. None of the verdicts is a judgement on whether the statement is true.

    mcp-tool

    {
      "type": "object",
      "required": [
        "statement",
        "source"
      ],
      "properties": {
        "source": {
          "type": "string",
          "description": "The public http(s) link the statement is supposed to come from."
        },
        "statement": {
          "type": "string",
          "description": "The words to check, as claimed. One claim at a time, up to 600 characters."
        }
      }
    }
    arguments 17 lines
  • search_transcripts unknown 16h ago

    Full-text search inside the whole transcripts of every podcast and video yank.info has yanked, not only their five lines (§10.424). Returns moments: the source, where in it (startSeconds, endSeconds), the words around the match (snippet, the match between « and »), a moment link that opens the source at that second, and yankThisPartUrl, which yanks the few minutes around it. The words are a machine transcript (representation: transcript), not a checked line: to quote one, yank that part or use check_quote. Supports quoted phrases and a leading minus.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 12,
          "maximum": 40,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Words, a name, or a quoted phrase, as it might have been said."
        }
      }
    }
    arguments 18 lines
  • get_yank reads unknown 12h ago

    Fetch a yank (five extracted lines from one source) by its slug, the last path segment of a yank.info/y/<slug> URL. Includes every line's verbatim flag, timestamp, moment link, surrounding context, permanent card URL, share image, plus the whole yank as Markdown.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "e.g. stanford-connect-the-dots-looking-1s52rgg"
        }
      }
    }
    arguments 12 lines
  • check_memory unknown 16h ago

    check_quote over a batch, for auditing what an agent wrote down earlier. Give it up to 10 remembered claims, each with the source it is attributed to, and it returns the same verdict and receipt for every one: FOUND, CLOSE MATCH, DISTILLED MATCH, NOT FOUND or CAN'T ESTABLISH, with where, the speaker and the class of that claim, the passage, which representation was read and how much of it, and when. Reach for it when a note, a memory store or a shared workspace has accumulated claims nobody re-checked, and you want the ones no source supports. The summary counts verdicts and lists the claims that came back NOT FOUND; it is deliberately not a score, a percentage or a trust rating, because a NOT FOUND is bounded to the representation Yank read and is never a claim that the words were not said. A claim whose source is audio Yank would have to transcribe returns CAN'T ESTABLISH rather than being paid for. No model is consulted anywhere in this: every verdict resolves against the representation itself, and none of them is a judgement on whether a claim is true.

    mcp-tool

    {
      "type": "object",
      "required": [
        "claims"
      ],
      "properties": {
        "claims": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "statement",
              "source"
            ],
            "properties": {
              "id": {
                "type": "string",
                "description": "Optional. Your own identifier for this claim, echoed back so you can match the verdict to the note it came from."
              },
              "source": {
                "type": "string",
                "description": "The public http(s) link the claim is attributed to."
              },
              "statement": {
                "type": "string",
                "description": "The remembered words, as written down. Up to 600 characters."
              }
            }
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "The remembered claims to check, up to 10 per call. Each one is checked against its own source."
        }
      }
    }
    arguments 35 lines
  • search_lines reads unknown 12h ago

    Full-text search across every line yank.info has ever extracted. Returns quotable lines with a verbatim flag (true = literal substring of the source transcript; false = labeled paraphrase), the speaker/author, the source, a timestamp and a moment link where the source is a video, and the permanent card URL to cite. Supports quoted phrases and a leading minus to exclude a word.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 40,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Words, a name, a show, or a quoted phrase."
        }
      }
    }
    arguments 18 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 2b4addd21303802f.

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

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.