# Yank (remote · yank.info)

Five sourced lines from a video, podcast, article or PDF, and a check that a quote is in its source

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `yank.info`: 70/100 (this document), [markdown](https://verifymcp.io/servers/info-yank-yank/api-mcp.md), [page](https://verifymcp.io/servers/info-yank-yank/api-mcp)

## Channel facts

- Endpoint: `https://yank.info/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 924 tokens (~184/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http info-yank-yank 'https://yank.info/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "info-yank-yank": {
      "url": "https://yank.info/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "info-yank-yank": {
      "type": "http",
      "url": "https://yank.info/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.info-yank-yank]
url = "https://yank.info/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "info-yank-yank": {
      "type": "remote",
      "url": "https://yank.info/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add info-yank-yank --url 'https://yank.info/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  info-yank-yank:
    url: "https://yank.info/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "info-yank-yank": {
      "Transport": "http",
      "Url": "https://yank.info/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add info-yank-yank -t streamable-http -u 'https://yank.info/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "info-yank-yank": {
      "type": "http",
      "url": "https://yank.info/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 70)

First indexed and scored.

## MCP tools (5)

### `search_lines` (~112 tokens)

Search yanked lines

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.

Input parameters:

- `limit` (integer)
- `query` (string, required): Words, a name, a show, or a quoted phrase.

### `check_quote` (~371 tokens)

Check a statement against its source

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 (the claim is supported, not in the source's literal words), 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.

Input parameters:

- `source` (string, required): The public http(s) link the statement is supposed to come from.
- `statement` (string, required): The words to check, as claimed. One claim at a time, up to 600 characters.

### `get_yank` (~91 tokens)

Get one yank

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.

Input parameters:

- `slug` (string, required): e.g. stanford-connect-the-dots-looking-1s52rgg

### `get_lines_for_url` (~149 tokens)

Lines already yanked from a URL

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.

Input parameters:

- `url` (string, required): The source URL in any of its forms.

### `recent_yanks` (~40 tokens)

Recent yanks

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

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/info-yank-yank/api-mcp#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70

## Common questions

### 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 70 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 5 tools: search_lines, check_quote, get_yank, get_lines_for_url, recent_yanks. Their descriptions and schemas cost roughly 763 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://yank.info/api/mcp
- Website: https://yank.info/developers#mcp
- Changelog RSS feed: https://verifymcp.io/servers/info-yank-yank/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/info-yank-yank/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/info-yank-yank/api-mcp