Skip to main content
Glama
vivmuk

Medhā MCP

by vivmuk

Related Servers

Alternatives to Medhā MCP

No user-submitted related servers found.

    Related Servers

    TDQS

    B3.4/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools are clearly distinct by domain (chat, image, video, music, web, voice, crypto, x402). However, venice_chat and venice_responses overlap significantly — both are chat completions with nearly identical operator preferences and uncensored behavior. Similarly, venice_video_status/venice_music_status and venice_video_complete/venice_music_complete follow parallel but separate verbs that are easy to confuse across media types. The image_edit vs image_multi_edit distinction is reasonably clear, but chat vs responses and the parallel status/complete pairs introduce ambiguity.

    Naming Consistency4/5

    The naming follows a strong venice_<domain>_<action> pattern consistently (venice_image_generate, venice_video_status, venice_music_complete, venice_web_search). The domain prefix is uniformly applied to all 31 tools. Minor inconsistency: some tools use generic verbs (chat, asr, tts) while others use domain+verb, and venice_voice_clone uses 'manage' semantics differently from venice_image_styles. Overall highly predictable but with minor phrasing variations.

    Tool Count2/5

    31 tools is quite heavy for a single server surface. While the underlying Venice API is genuinely broad (chat, images, video, music, voice, web, crypto, x402 billing), the server bundles what could be several focused MCP servers into one, exceeding the comfortable range. The count feels bloated, especially with 5 different x402/crypto tools and 4 video tools plus 4 music tools that duplicate the lifecycle pattern.

    Completeness4/5

    The surface is remarkably comprehensive, covering chat, images (generate/edit/multi-edit/upscale/remove-bg/styles), video (generate/status/complete/quote), music (generate/status/complete/quote), voice (TTS/asr/clone), text parsing, web search/scrape, embeddings, and x402 billing. Minor gaps: text parsing accepts URLs but there's no direct file-upload handler for documents, and there's no image generation status polling since it's synchronous, which is fine. The x402 billing flow stops at step-1 direction without steps 2-3, which is acknowledged as external.

    Maintenance

    ActivityStale
    ResponsivenessNo issues