system-brain-mcp
Related Servers
Alternatives to system-brain-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceExposes nine read-only tools that let a coding agent audit a repository for fabricated fallbacks, hollow or weakened tests, silently disabled checks and missing authorization scoping. Agents can run the six deterministic engines on changed or whole-repository code and get structured findings back without modifying anything.10177 PyPI1Apache 2.0- AlicenseNot gradedqualityBmaintenanceA read-only MCP service for production troubleshooting that lets you register database, log, code, and message-queue connections in a web console, then have AI clients query them safely by target name. Models never supply hosts, accounts, or passwords themselves, and all operations are restricted to a read-only whitelist with audit logging.603 PyPI3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to analyze repository architecture, changed-file and diff impact, dependency and endpoint exposure, API contract compatibility, architecture boundaries, bounded capacity simulations, and security/quality evidence through MCP tools.3Apache 2.0
- FlicenseAqualityBmaintenanceProvides coding agents read-only access to Depot's CI failure diagnoses, container build forensics, run history, cache effectiveness, registry contents, and usage data through MCP tools.2857 npm1-
- AlicenseNot gradedqualityBmaintenanceProvides read-only production observability through a small set of tools for health, job status, latest data, approved logs, and deployment metadata, enabling AI planning and review without a production write path.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and engineers to query evidence-qualified cross-boundary architecture relationships, binding pictures, drift, and supporting evidence from declared and observed architecture data through read-only MCP tools.10Apache 2.0
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action: deploys, backlog, DB schema, ML models, analytics, architecture docs, fabrication audit, lenses, roadmap, recommend, and reframe. Descriptions clearly separate related tools like db_schema vs. analytics and backlog vs. roadmap.
All tools share the 'brain_' prefix, creating a clear family, but the suffixes mix nouns (backlog, analytics, architecture), verbs (recommend, reframe), and query-like phrases (where_deploys). This is mostly consistent but not a strict verb_noun pattern.
11 tools is well within the ideal range for a decision-support brain. Each tool covers a discrete capability needed for the apparent domain, and none feel redundant or superfluous.
The tool surface covers the full gather-analyze-recommend-reframe loop using available evidence sources. Minor gaps exist—e.g., no direct GitHub issue/PR detail lookup beyond the backlog aggregate, and no tool for explicit doc searches—but agents can work around these.