A
licenseNot graded
qualityB
maintenanceViral-content intelligence for AI agents — 7 read-only MCP tools for TikTok/YouTube hook scoring, virality prediction, trend analysis, and viral template search, with evidence-layer scoring.
MIT
moreel
by medaharrat
Related Servers
Alternatives to moreel
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceGives MCP clients access to YouTube video transcripts and metadata. It lets AI agents read and summarize video content from a URL.8 npmMIT
- AlicenseAqualityBmaintenanceEnables agents to turn public video links into timestamped transcripts, chapters, and clip suggestions for YouTube, Twitch, Kick, and TikTok.3MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server agent that enables analysis of YouTube videos by extracting transcripts, generating summaries, and creating chapter timestamps. It allows users to interact with video content through natural language to perform tasks such as writing social media posts.Apache 2.0
- FlicenseAqualityDmaintenanceEnables AI agents to semantically search, ask questions about, and analyze videos, with persistent memory and social media import capabilities.182-
- AlicenseNot gradedqualityBmaintenanceFetches YouTube video transcripts with timestamps and provides them to LLM agents via MCP, enabling natural language access to video content.101 npm4MIT
TDQS
A4.7/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clearly distinct role: transcribe_video for audio-only transcription, understand_video for full multimodal processing, and the remaining tools operate on the returned video_id for search, evidence, timeline, or semantic mapping. Even the overlapping transcribe/understand pair is explicitly differentiated by use case, and search_video vs find_moment are separated by exhaustive vs. single-best results.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern (transcribe_video, understand_video, search_video, find_moment, get_video_timeline, get_video_map, get_video_entity, get_video_evidence). The pattern is uniform and predictable, making it easy for an agent to infer function from the name alone.
Tool Count5/5
Eight tools is well within the ideal 3–15 range and feels well-scoped for a video understanding server. Each tool has a specific place in the pipeline (ingest, search, timeline, semantic map, evidence lookup) without redundancy or bloat.
Completeness5/5
The tool surface covers the full workflow: ingest a video (transcribe_video/understand_video), explore it (search_video, find_moment, get_video_timeline), and dig into semantic relationships (get_video_map, get_video_entity, get_video_evidence). The design anticipates the questions agents will ask and provides no dead ends—every returned video_id can be used by downstream tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues