Primate Intelligence
OfficialRelated Servers
Alternatives to Primate Intelligence
No user-submitted related servers found.
Related Servers
- MIT

VZT Video-Intelofficial
AlicenseNot gradedqualityCmaintenanceSelf-hosted video intelligence pipeline that turns video into structured, citable, queryable JSON scene graphs, enabling AI assistants to analyze and search across video libraries without re-processing.9 npm1MIT- AlicenseNot gradedqualityDmaintenanceA video analysis system that uses AI vision models to process, analyze, and query video content through natural language, enabling users to search videos by time, location, and content.7MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for 4K video generation using Google VEO 3.1 — text-to-video, image-to-video, video extension, and frame interpolation.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for comprehensive video analysis — AI-powered transcription, visual frame analysis, and metadata extraction from 1000+ platforms.1MIT
- AlicenseAqualityAmaintenanceMCP server for video analysis — extracts transcripts, key frames with OCR, and annotated timelines from video URLs. Supports Loom and direct video files (.mp4, .webm). Zero auth required.48834 npm61MIT
TDQS
Scored across 10 tools
Most tools are clearly distinct: create_analysis vs create_analysis_batch, validate_analysis vs create_analysis, and get_analysis vs wait_for_analysis all have well-defined boundaries. The only potential confusion is between get_usage and get_credits, which both return credit balance, but their descriptions differentiate usage meters from transaction ledger.
All tools follow a consistent verb_noun pattern with lowercase and underscores. Verbs are limited to get, create, validate, wait_for, and list, and each noun is clear. There are no mixed conventions or stylistic deviations.
With 10 tools, the server is well-scoped for a video analysis API. Each tool serves a distinct purpose in the workflow: video ingestion, analysis creation (single/batch), validation, polling, retrieval, model listing, credit management, and test fixture access. The count feels neither sparse nor bloated.
The core workflow (create video, validate prompt, create analysis, wait for result, fetch result) is covered, including batch and dry-run operations. However, there are notable gaps: no way to retrieve or delete a video by ID, no list of analyses, no cancellation for a running analysis, and no explicit check for video readiness before analysis creation. These gaps could cause agent failures in multi-step workflows.