Fetch vs Scribefy MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Fetch vs Scribefy MCP
In-depth architectural comparison of the Fetch and Scribefy MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Fetch
Search & Data Extraction · Local stdio
Quality: 89/100 (Excellent) | Auth: No auth required
Scribefy MCP
Search & Data Extraction · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose Fetch if you need specialized Search & Data Extraction tools running via a local process. Choose Scribefy MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Fetch when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Fetch is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Scribefy MCP belongs to Search & Data Extraction using local stdio subprocess. Select Fetch when you need capabilities focused on search & data extraction and Scribefy MCP when you require tools for search & data extraction.
Search for nodes in the knowledge graph based on a query
open_nodes
Open specific nodes in the knowledge graph by their names
Scribefy MCP Tools (4)
extract_transcript
Pulls the transcript of a YouTube video and returns it as Markdown with timestamps. Use this whenever the user provides a YouTube URL and wants to summarise, quote, search, or otherwise process the video's spoken content.
Costs credits on first fetch (1 credit ≤15min, 2 credits 15–45min, 4 credits 45min–2h, 8 credits 2h+). Cached extractions are free — videos other Scribefy users have already extracted are cached for 30 days.
Returns the title, channel, duration, language, and the transcript itself split into segments with clickable timestamps.
search_videos
Search YouTube for videos matching a query string. Returns up to `limit` results (default 10, max 25) with title, channel, duration, view count, and URL. Free — no credits charged. Use this when the user asks 'find me videos about X' before chaining into extract_transcript on a specific result.
get_video_metadata
Look up title, channel, duration, view count, upload date, and available caption tracks for a video. Does NOT pull the transcript — use extract_transcript for that. Free — no credits charged. Useful to inspect a video before deciding whether to extract, or to discover which caption languages are available.
get_related_videos
Return the videos YouTube recommends after a given video — the 'Up next' / 'Related' feed. Returns up to `limit` results (default 10, max 25). Free — no credits charged. Use this to expand research from a single starting video, or to find adjacent content.