Youty MCP server — exposes the Youty vault index (sqlite-vec + FTS5) to MCP-compatible AIs.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"youty-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# youty-mcp Local MCP server that exposes the Youty vault's vector index to any MCP-compatible AI (Claude Desktop, Claude Code, Cursor). ## What it does Seven tools, hybrid dense + BM25 retrieval over your captured YouTube / Instagram / TikTok videos, plus joint text → frame retrieval via Google's SigLIP-Base-Patch16-224 (Apache-2.0). Search runs locally on macOS; latency depends on model warm-up, hardware, and vault size. | Tool | Returns | |---|---| | `search(query, k=15, platform?, since_iso?)` | hybrid dense + BM25 + RRF over transcript chunks; top-k results with `frame` paths + `video_md_path` | | `search_frames(query, k=10, platform?)` | SigLIP-Base joint text→image; top-k frame matches with parent video metadata | | `get_transcript(video_id)` | full `video.md` + parsed frontmatter — the whole video into context | | `get_video(video_id)` | frontmatter + folder listing + frame paths | | `view_frames(video_id, frame_ms?, max_frames=6)` | the frame JPEGs themselves, as MCP image content — viewable in **any** client | | `list_videos(platform?, channel?, limit=100)` | newest-first listing | | `find_similar(video_id, k=10)` | nearest videos by averaged body-chunk vectors | **The loop:** `search` finds the relevant moments → `get_transcript` pulls the words into context → `view_frames` loads the matching frames into the model's vision. `search` / `search_frames` also return raw frame *paths*, which require a client with local-file access; `view_frames` returns the images inline, so the visual half of the loop works in Claude Desktop, Cursor, and Claude Code alike. **On-screen text.** `search` covers both what a video *said* and what it *showed*: each result's `chunk.type` is `body`/`description`/`header` (spoken + metadata) or **`frame_text`** — text recognized on-screen via on-device OCR (slides, code, terminal output, labels). A `frame_text` hit means the answer was visible in the video; pair it with `view_frames` to see that moment. ## Install ```bash cd …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.