A
licenseA
qualityA
maintenanceProvides 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.
28
55 npm
1
-
system-brain-mcp
by QEbellavita
Related Servers
Alternatives to system-brain-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to audit a Next.js codebase read-only, checking routes, Prisma models, environment variables, and locale consistency via MCP tools.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- FlicenseAqualityBmaintenanceA read-only MCP server that gives AI coding agents structured access to a project's source code, architecture, documentation, and Git context through 16 tools for searching, reading, and comparing evidence without modifying files.16-
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to record auditable work ledgers with evidence chains, from contract to proof packet, via MCP tools for file scanning, code review, and issue triage.49MIT
- AlicenseAqualityCmaintenanceEnables agents to audit and safeguard repositories by detecting dependency pinning issues, license compliance problems, hardcoded secrets, and dead code through MCP tools.4MIT
TDQS
A4/5.0
Scored across 11 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivitySlowing
ResponsivenessNo issues