genesis-ai-bridge
Related Servers
Alternatives to genesis-ai-bridge
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceA privacy-first MCP server that provides local LLM-enhanced tools for code analysis, security scanning, and automated task execution using backends like Ollama and LM Studio. It enables symbol-aware code reviews and workspace exploration while ensuring that all code and analysis remain strictly on your local machine.36ISC
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server using Ollama for local AI-powered code analysis, refactoring, and optimization. Integrates with VS Code via Continue or Roo.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for local codebase analysis, enabling semantic code search, impact analysis, and pack-scoped retrieval with cited file:line results.Apache 2.0
- FlicenseBqualityCmaintenanceProvides a minimal MCP server with safe tools for AI assistants to search project files, read files, search local documentation, and run pre-approved checks within a single project directory.4-
- AlicenseNot gradedqualityBmaintenanceStandalone MCP server that provides security scanning, project mapping, and vulnerability fix generation to AI coding assistants.155 npm2MIT
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that scans code for security issues (secrets, dependencies, configurations, risky patterns) and integrates with GitHub Copilot in VS Code for automated pre-commit reviews.-
TDQS
Scored across 6 tools
bridge_health and bridge_doctor both perform read-only health/diagnostics, creating potential confusion about which to use. The other tools are distinct in purpose, but this overlap reduces clarity.
All tools use snake_case, but the naming pattern is mixed: some are verb_noun (run_shared_file, propose_corrections, apply_corrections) while others are noun-like (bridge_health, bridge_doctor, ollama_models). This inconsistency makes the set less predictable.
With 6 tools, the server is well-scoped for its purpose—health checks, model listing, analysis, and correction workflow. Each tool has a clear role, and the count is within the ideal range.
The core workflow (check health, list models, run analysis, propose corrections, apply corrections) is covered, but there is no tool to retrieve past proposals or correction history, which is a minor gap.