Skip to main content
Glama
NawafSheikh

portfolio-mcp

by NawafSheikh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to portfolio-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-repo-health

      ashwinmridul
      A
      license
      B
      quality
      C
      maintenance
      Scores local git repositories for README substance, license, package description, TypeScript config, tests, and GitHub Actions, providing a numbered hygiene report.
      2
      MIT

    • codescan-mcp

      yifanyifan897645
      A
      license
      Not graded
      quality
      D
      maintenance
      Scans codebases for TODOs, FIXMEs, code complexity, file stats, and dependencies, generating a health report with a letter grade. Zero configuration required.
      8 npm
      MIT

    • RepoFather

      its-imad
      A
      license
      Not graded
      quality
      B
      maintenance
      Scans repositories to produce a readiness score and actionable fixes across positioning, tryability, community, MCP, and monetization, plus generates launch assets and sponsor-tier ideas.
      2 npm
      MIT

    • Project Context MCP Server

      wblair8689
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides unified project context and monitoring capabilities including project health metrics, build diagnostics, Git integration, and infrastructure validation to initialize development sessions with comprehensive project information.
      -

    • worktree-orbit-mcp

      mrfentmen
      F
      license
      A
      quality
      C
      maintenance
      Provides read-only inspection of Git worktree topology, reporting aggregate counts and statuses (clean, dirty, detached, locked, prunable). Ensures safety by limiting commands to a configured root and never exposing paths or content.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources