Skip to main content
Glama
Godofdeath1709

pathpilot-mcp-server

by Godofdeath1709
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to pathpilot-mcp-server

No user-submitted related servers found.

    Related Servers

    • CampusMind-AI

      Maheshdayyala
      A
      license
      A
      quality
      B
      maintenance
      A calculator-focused MCP server template with tools, resources, and prompts built on NitroStack.
      22
      MIT

    • amrita-companion-mcp

      aksharasuresh05-rgb
      F
      license
      A
      quality
      C
      maintenance
      A minimal NitroStack starter template with a calculator module including tools, resources, and prompts for learning MCP server fundamentals.
      4
      -

    • NitroStack Calculator MCP

      Tarika06
      F
      license
      C
      quality
      C
      maintenance
      A minimal MCP server template for learning NitroStack fundamentals, featuring a calculator module with tools, resources, and prompts.
      9
      -

    • NitroStack Calculator MCP

      VRDhwaraganath
      F
      license
      B
      quality
      C
      maintenance
      A minimal MCP server template for learning NitroStack fundamentals, featuring a calculator module with tools, resources, and prompts.
      6
      -

    • NitroStack Calculator MCP

      Rookie-1207
      F
      license
      B
      quality
      C
      maintenance
      A minimal MCP server template for learning NitroStack, featuring a calculator module with tools, resources, and prompts for arithmetic operations.
      4
      96 npm
      -
    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

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct resource or stage of the analysis pipeline. The only potential confusion is between generate_evidence_cards and get_roadmap_signal, both of which consume an analysisId but produce different outputs; the descriptions make this clear.

    Naming Consistency4/5

    All tool names follow a verb_noun pattern with underscores, which is consistent in style. The verbs vary (analyze, get, compare, generate) but are all action-oriented and the pattern is predictable.

    Tool Count5/5

    Six tools is well within the ideal range for a specialized server. Each tool has a clear role in the workflow, and none are redundant or redundant-feeling.

    Completeness4/5

    The server covers the full lifecycle from raw profile/repo input to analysis and actionable outputs. Minor gaps exist, such as no explicit 'get full analysis' tool or list of prior analyses, but the core workflow is complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources