Yank
by yank.info · remote · no sign-in to list tools · v1.1.0 · published by info.yank
Five sourced lines from a video, podcast, article or PDF, and a check that a quote is in its source
7 tools: 3 change things and 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things3Claude Code: ask: see these tools
- Only reads4Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http yank https://yank.info/api/mcpFindings
Matches of fixed checks, with the text they matched.
- Warncheck_quote
The server marks "check_quote" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input takes a statement or command to run (input.statement), which can change anything it can reach.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
7 tools
Changes things 3Claude Code: ask
check_memorycheck_quote over a batch, for auditing what an agent wrote down earlier.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check remembered claims against their sources
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
check_quoteYank Check: a statement and the source it is supposed to come from, in; a verdict and a receipt, out.Reads text others write1 finding
Why it is in this group
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_quote" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input takes a statement or command to run (input.statement), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a statement against its source
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
recent_yanksThe newest yanks in the library, one card each (rank-1 line, author, source type, URL).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The newest yanks in the library, one card each (rank-1 line, author, source type, URL).
Annotations the server declares
- title: Recent yanks
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Claude Code: allow, ask for 1 outbound
get_lines_for_urlAsk before you extract: everything yank.info already holds from one source URL.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_lines_for_url" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_lines_for_url" says "get" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Lines already yanked from a URL
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_yankFetch a yank (five extracted lines from one source) by its slug, the last path segment of a yank.info/y/<slug> URL.Reads text others writeNo findings
Why it is in this group
- The name "get_yank" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one yank
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_linesFull-text search across every line yank.info has ever extracted.No findings
Why it is in this group
- The name "search_lines" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search yanked lines
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_transcriptsFull-text search inside the whole transcripts of every podcast and video yank.info has yanked, not only their five lines (§10.424).No findings
Why it is in this group
- The name "search_transcripts" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search inside what Yank has read
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 14:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- none
- RFC 9728 protected resource metadata
- none
- Authorization servers
- none
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://yank.info/api/mcp: tools/list returned 7 tools to an anonymous client, including check_quote (write), check_memory (write), recent_yanks (write)
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http yank https://yank.info/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__yank__search_lines",
"mcp__yank__search_transcripts",
"mcp__yank__get_yank"
],
"ask": [
"mcp__yank__check_quote",
"mcp__yank__check_memory",
"mcp__yank__get_lines_for_url",
"mcp__yank__recent_yanks"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as yank. Review it before you use it.
Capability tags behind 4 rules
- mcp__yank__check_quote untrusted-input
- mcp__yank__check_memory untrusted-input
- mcp__yank__get_yank untrusted-input
- mcp__yank__get_lines_for_url untrusted-input, outbound