A
licenseB
qualityC
maintenanceScores local git repositories for README substance, license, package description, TypeScript config, tests, and GitHub Actions, providing a numbered hygiene report.
2
MIT
portfolio-mcp
by NawafSheikh
Related Servers
Alternatives to portfolio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceScans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceScans repositories to produce a readiness score and actionable fixes across positioning, tryability, community, MCP, and monetization, plus generates launch assets and sponsor-tier ideas.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only, workspace-bound inspection of repositories and log files, returning JSON reports with file counts, largest files, TODO/FIXME markers, and warning/error counts.MIT
- AlicenseAqualityCmaintenanceScans a repository for maintenance toil (flaky tests, expiring certificates, TODO rot, dead flags, etc.) and returns a prioritized queue with a credit ledger to track who cleared what.71MIT
- AlicenseNot gradedqualityCmaintenanceEnables running deterministic package.json checks for Next.js, Expo, and Convex projects via a read-only stdio tool, returning JSON findings usable by CI and coding agents.249 npmMIT
TDQS
B3.4/5.0
Scored across 12 tools
Disambiguation2/5
Several tools have overlapping boundaries. git_overview and stale_projects both identify projects with no commits in 90+ days, and deployment_map and list_projects both provide project lists with deployment information. This creates real ambiguity for an agent choosing between them.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern like list_projects, get_project, search_projects, check_health, and find_opportunities. The exceptions are deployment_map and git_overview, which are noun phrases rather than verb-led names, but the naming remains largely predictable and readable.
Tool Count4/5
Twelve tools is within a reasonable range for a portfolio analysis server and each tool serves a distinct functional area overall. The count is slightly higher than necessary due to redundant stale-project logic and the partial overlap between deployment_map and list_projects, but it is not excessive.
Completeness4/5
The tool surface covers project discovery, deep inspection, deployment status, health checks, git hygiene, dependency vulnerabilities, revenue analysis, and opportunity ranking. Minor gaps exist, such as no bulk dependency scan across all projects and no direct action/deploy tools, but these are workable within the server's apparent analysis-focused purpose.
Maintenance
ActivityStale
ResponsivenessNo issues