godmod3-mcp
Related Servers
Alternatives to godmod3-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that bridges multiple AI clients (Claude, Gemini, Codex, OpenCode) so they can call each other as tools.123 npm72-
- AlicenseAqualityBmaintenanceBridges MCP clients to the DeepSeek API for chat completions and model discovery, with an optional locked-down bridge that delegates prompts to local CLI harnesses like Claude, Codex, or opencode.437 npmMIT
- FlicenseNot gradedqualityDmaintenanceBridges Google's Gemini CLI with MCP-compatible clients and integrates OpenRouter API for access to 400+ AI models. Provides 33 specialized tools enabling multi-AI workflows, collaborations, and debates between Claude, Gemini, and other LLMs.142-
- AlicenseNot gradedqualityCmaintenanceBridges MCP-compatible AI clients to over 100 Hermes Agent skills for web browsing, file management, code execution, GitHub operations, and more.1MIT
- AlicenseNot gradedqualityAmaintenanceMulti-server MCP tool bridge that exposes banking, email, calendar, and custom API tools for AI clients via the Model Context Protocol.1,383 npmMIT
- FlicenseNot gradedqualityDmaintenanceA modular MCP server that provides AI agents with cognitive memory, local system access, and secure remote execution capabilities through three integrated layers (Brain, Master, Remote).-
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes, such as single_chat vs. ultraplinian_chat vs. consortium_chat, and parseltongue_encode vs. parseltongue_detect. Minor overlap exists between health_check and server_info (both relate to connectivity/info) and between dataset_stats and research_stats (both provide statistics but on different datasets), but these are distinguishable with careful reading.
Naming conventions are mixed: some tools follow verb_noun patterns (list_models, get_tier, transform_text, submit_feedback, export_dataset), while others use noun_verb or compound nouns (health_check, parseltongue_encode, parseltongue_detect, server_info, dataset_stats). All names are readable and use snake_case, but the inconsistent verb placement and noun-only names prevent a higher score.
With 17 tools, the server falls into the 'heavy' range (16-25). The tool count is justified by the broad scope of the API, covering chat, optimization, text transformation, and research, but it still feels slightly bloated and could be consolidated by merging some informational tools or research stats endpoints.
The tool surface is largely complete for the stated domain: it covers chat (single, ULTRAPLINIAN, CONSORTIUM), AutoTune analysis, Parseltongue encoding/detection, STM transformation, feedback, dataset export, and research querying. Minor gaps include no Parseltongue decoding and no dataset upload/management, but these are not critical for the core API usage.