Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.not0lucky/tubescout

NPM · TUBESCOUT · SCANNED SEP 20

YouTube as a research engine: keyless search, video intel, resilient transcripts, demand signals.

Available components

+3 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 564 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.not0lucky/tubescout MCP server?

io.github.not0lucky/tubescout runs locally as an npm package, launched with npx -y tubescout. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tubescout

# add to Claude Code
claude mcp add not0lucky-tubescout -- npx -y tubescout
// .cursor/mcp.json
{
  "mcpServers": {
    "not0lucky-tubescout": {
      "command": "npx",
      "args": [
        "-y",
        "tubescout"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "not0lucky-tubescout": {
      "command": "npx",
      "args": [
        "-y",
        "tubescout"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add not0lucky-tubescout -- npx -y tubescout
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "not0lucky-tubescout": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tubescout"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add not0lucky-tubescout --command npx --arg -y --arg tubescout
# ~/.hermes/config.yaml
mcp_servers:
  not0lucky-tubescout:
    command: "npx"
    args: ["-y", "tubescout"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "not0lucky-tubescout": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tubescout"
      ]
    }
  }
}
# add to Vellum
assistant mcp add not0lucky-tubescout -t stdio -c npx -a -y tubescout
// mcp.json
{
  "mcpServers": {
    "not0lucky-tubescout": {
      "command": "npx",
      "args": [
        "-y",
        "tubescout"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +4
    • Stability: unverified → 0.27 functional
Diagnostics

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 20 Sept 2026 · Analysed npm/tubescout@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 99 packages
Packages resolved 99
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~564 tokens

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 →

Tool Tokens
get_channel_videos ~76

Channel metadata (name, subscribers, description) plus its recent uploads with views — enough to read a channel's strategy, cadence, and what performs.

NameTypeReqDescription
channelstringyesChannel ID (UC…), @handle, or channel URL
maxVideosintegerHow many recent videos to return (default 20)

No output schema declared.

No examples provided.

get_search_suggestions ~75

YouTube's autocomplete for a seed term — a direct read on real search demand. Use for keyword research: seed a niche term, get what people actually type. Chain suggestions of suggestions to map a topic space.

NameTypeReqDescription
querystringyesSeed term, e.g. 'stamp identifier' or 'n8n'

No output schema declared.

No examples provided.

get_transcript ~119

Fetch a video's transcript as clean plain text. Resilient: tries InnerTube, then the timedtext caption track, then local yt-dlp if installed. Long transcripts are chunked — check totalChars and call again with offsetChars to continue.

NameTypeReqDescription
languagestringPreferred caption language code (default 'en')
maxCharsintegerChunk size (default 60000)
offsetCharsintegerCharacter offset to resume a chunked transcript
videostringyesVideo ID or any YouTube URL

No output schema declared.

No examples provided.

get_transcripts ~86

Batch transcript fetch (max 10 videos, 3 at a time). Per-video failures don't kill the batch — failed entries carry an error field. Each transcript is truncated to fit; use get_transcript with offsetChars for full text of long ones.

NameTypeReqDescription
languagestringPreferred caption language code (default 'en')
videosarrayyesVideo IDs or URLs

No output schema declared.

No examples provided.

get_video ~77

Full metadata + engagement for one video: title, channel, publish date, views, likes, likesPer1kViews (resonance signal, typical range 10-50), category, keywords, description, hasCaptions.

NameTypeReqDescription
videostringyesVideo ID or any YouTube URL (watch, youtu.be, shorts)

No output schema declared.

No examples provided.

search_videos ~131

Search YouTube for videos (no API key). Returns id, title, channel, published, views, duration, snippet per hit. Use filters to narrow: uploadDate for recency, sortBy view_count to find what performs.

NameTypeReqDescription
durationstringshort <4min, medium 4-20min, long >20min
maxResultsintegerMax hits to return (default 15)
querystringyesSearch query
sortBystringResult ordering (default relevance)
uploadDatestringOnly videos uploaded within this window

No output schema declared.

No examples provided.

Common questions

What is the io.github.not0lucky/tubescout MCP server?

io.github.not0lucky/tubescout is an MCP server listed in the public MCP registry as io.github.not0lucky/tubescout. YouTube as a research engine: keyless search, video intel, resilient transcripts, demand signals. This page covers its npm package (tubescout).

Is the io.github.not0lucky/tubescout MCP server safe to use?

io.github.not0lucky/tubescout scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.not0lucky/tubescout MCP server expose?

io.github.not0lucky/tubescout exposes 6 tools: search_videos, get_video, get_transcript, get_transcripts, get_channel_videos, get_search_suggestions. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.

Is the io.github.not0lucky/tubescout MCP server still maintained?

io.github.not0lucky/tubescout is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.not0lucky/tubescout MCP server under?

io.github.not0lucky/tubescout declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.