A
licenseNot graded
qualityC
maintenanceCross-stack MCP server that scans frontend and backend code together, detects mismatches like phantom calls, dead endpoints, and field drift, and provides a full-stack health audit.
6 npm
1
MIT
BackendMax
by rish-e
Related Servers
Alternatives to BackendMax
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that provides code validation rules and analysis for various stacks/frameworks, enabling automated code reviews and reporting directly from VS Code and other editors.-
- AlicenseAqualityCmaintenanceMCP server providing diagnostic tools to analyze software architecture, security, REST API compliance, and dependencies for multiple programming languages. Enables AI agents to run scans and audits on codebases.7MIT
- FlicenseNot gradedqualityBmaintenanceLocal MCP server for static Python/TypeScript code audits, Playwright test generation, and SDLC health checks with a 0-100 quality score.-
- FlicenseAqualityNot gradedmaintenanceStatic analysis engine that detects schema mismatches between data producers (like MCP servers) and consumers (like client code), preventing runtime errors by validating contracts at development time.11-
- AlicenseAqualityAmaintenanceLocal-first production-readiness MCP server for AI-built apps. It runs read-only checks, produces an evidence-based readiness score, and guides fixes before launch.115Apache 2.0
TDQS
A3.6/5.0
Scored across 41 tools
Disambiguation4/5
Most tools have distinct purposes, but some overlap exists (e.g., multiple audit tools for security, performance, etc.). Descriptions help differentiate, but an agent might still confuse similar-sounding tools like run_safety_check and run_diagnosis.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_ledger, fix_issue, scan_routes). No mixing of conventions, making it easy for an agent to predict tool names.
Tool Count3/5
With 41 tools, the server feels overloaded despite covering a broad domain. While each tool has a rationale, the count exceeds typical well-scoped ranges (3-15), risking agent confusion and slow selection.
Completeness4/5
The tool set comprehensively covers backend auditing, diagnosis, testing, and contract checking. Minor gaps exist (e.g., no tool for monitoring or deployment audit), but core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessUnresponsive