Loading ToolBench
Omnidev GODMODE MCP Server: Unified Full Stack, DevOps, and AI Systems Architect. Operates as a global-scale, security-first, automation-driven meta-engineering entity.
This MCP server has critical definition quality issues. Tool definitions are extracted from a configuration file (.kiro/settings/mcp.json) rather than from explicit source code implementations. No input schemas are visible anywhere in the provided source. Descriptions exist but are extremely generic and fail to guide LLM tool selection. The server claims 20 tools across ambitious domains (ML analysis, DevOps orchestration, security audits, infrastructure-as-code) but provides NO evidence of actual implementation, only tool names and trivial descriptions. The 'ai_assistant_ml_server.py' file is referenced but not shown, making it impossible to verify parameter schemas, error handling, or output structure. This is a critical red flag: tool definitions without implementation code cannot be trusted.
Integrate AI/ML capabilities into systems
Analyze and evaluate system architecture
Validate system compliance with standards and regulations
Orchestrate DevOps operations and infrastructure management
Generate technical documentation automatically
Fetch data from HTTP endpoints
Retrieve documentation for system components
CRITICAL: No input schemas visible for ANY tool. All schema scores are 0. Tool definitions in .kiro/settings/mcp.json list only names and descriptions, actual parameter schemas, types, and constraints are not provided.
CRITICAL: Tool descriptions are generic, non-actionable, and fail to guide LLM selection. Example: 'Analyze emotional content from text or audio input using machine learning models' (74 chars) does not explain WHEN to use this vs other tools, what input format is expected, what output structure to expect, or any prerequisites.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 31 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Retrieve the current status and health of ML subsystems
Define and manage infrastructure using code
List available entities in the system
Analyze emotional content from text or audio input using machine learning models
Analyze reasoning patterns and logic chains in AI/ML systems
Extract learning insights and patterns from historical data using machine learning
Generate personality profile analysis using machine learning
Generate predictions from ML models based on input data
Automate machine learning pipeline creation and execution
Search through system documentation
Perform security audits and vulnerability assessments
Design and architect system components and infrastructure
Test and validate command reasoning logic
CRITICAL: Source code implementation not provided. Only tool names and descriptions from .kiro/settings/mcp.json are visible. The actual 'ai_assistant_ml_server.py' file is referenced but contents not shown, making it impossible to verify parameter validation, error handling, output structure, or even if these tools are actually implemented.
HIGH: Four tools (devops_orchestration, ai_integration, ml_pipeline_automation, infrastructure_as_code) are marked WRITE risk but descriptions do not declare this or explain what state they modify. No mention of confirmation, dry-run, or recovery steps for destructive operations.
HIGH: No parameter descriptions visible. Without parameter schemas and descriptions, LLMs cannot infer what inputs each tool expects, their types, valid ranges, or format requirements. A tool like 'devops_orchestration' could accept dozens of parameters, all unknown.
HIGH: No output schemas documented. LLMs have no way to know what fields to expect from tool results, making it impossible to chain tool calls or extract required IDs for downstream operations.
MEDIUM: Overly ambitious tool set (20 tools across ML, DevOps, security, infra-as-code) with no evidence of implementation depth. Suggests aspirational scope rather than production-ready functionality. High risk of incomplete or stub implementations.
MEDIUM: Tool 'system_design' lacks a clear verb prefix and is vague. Does it design at the component level, enterprise level, or microservice level? 'design' alone does not distinguish this from 'architecture_analysis'. This violates name clarity principles.
MEDIUM: Configuration references an 'AURA_DEV_CONFIG' environment variable with an embedded 'GODMODE' persona directive. This suggests prompt injection vulnerability and raises concerns about security boundaries. MCP tools should not embed role-play or persona instructions that override agent safety guidelines.