Yank
REMOTE · YANK.INFO
Five sourced lines from a video, podcast, article or PDF, and a check that a quote is in its source
Available components
Last scanned (19 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1531 tokens (~218/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://yank.info/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yank.info | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 6be5bf4afaa694a2f96641e8151f67041f8 |
| SANs: yank.info | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yank.info. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| info. | DS published | 9986 | 8 | Verified |
| yank.info. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://www.youtube.com https://www.youtube-nocookie.com https://plausible.io; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://img.youtube.com https://i.ytimg.com; font-src 'self' data:; connect-src 'self' https://huggingface.co https://*.hf.co https://plausible.io https://video.twimg.com; media-src 'self' blob: https:; frame-src https://www.youtube-nocookie.com https://www.youtube.com https://www.tiktok.com https://platform.twitter.com; worker-src 'self' blob:; manifest-src 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yank.info/api/mcp | Verified | 200 | |
| http (plaintext) | http://yank.info/api/mcp | HTTPS enforced | 308 | https://yank.info/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_memory Check remembered claims against their sources ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | The remembered claims to check, up to 10 per call. Each one is checked against its own source. |
No output schema declared.
No examples provided.
check_quote Check a statement against its source ~405
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 sha256, the fingerprint of the exact text read), the checker's version (checker), 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.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | The public http(s) link the statement is supposed to come from. |
| statement | string | yes | The words to check, as claimed. One claim at a time, up to 600 characters. |
No output schema declared.
No examples provided.
get_lines_for_url Lines already yanked from a URL ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The source URL in any of its forms. |
No output schema declared.
No examples provided.
get_yank Get one yank ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | e.g. stanford-connect-the-dots-looking-1s52rgg |
No output schema declared.
No examples provided.
recent_yanks Recent yanks ~40
The newest yanks in the library, one card each (rank-1 line, author, source type, URL).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
search_lines Search yanked lines ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words, a name, a show, or a quoted phrase. |
No output schema declared.
No examples provided.
search_transcripts Search inside what Yank has read ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words, a name, or a quoted phrase, as it might have been said. |
No output schema declared.
No examples provided.
How do I install the Yank MCP server?
Yank is a hosted endpoint at https://yank.info/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · yank.info
claude mcp add --transport http info-yank-yank 'https://yank.info/api/mcp'
What is the Yank MCP server?
Yank is an MCP server listed in the public MCP registry as info.yank/yank. Five sourced lines from a video, podcast, article or PDF, and a check that a quote is in its source. This page covers its hosted endpoint (https://yank.info/api/mcp).
Is the Yank MCP server safe to use?
Yank scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Yank MCP server expose?
Yank exposes 7 tools: search_lines, search_transcripts, check_quote, check_memory, get_yank, and 2 more. Their descriptions and schemas cost roughly 1,222 tokens of context every time the server is loaded.
Does the Yank MCP server require authentication?
No. We connected to Yank without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Yank MCP server still maintained?
Yank is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Yank MCP server?
VerifyMCP ran 13 checks on Yank, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.