Skip to main content
Glama
kishan-learningai

GH-600 MCP Server Lab

by kishan-learningai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GH-600 MCP Server Lab

No user-submitted related servers found.

    Related Servers

    • Basic MCP Server

      gurdasnijor
      A
      license
      Not graded
      quality
      D
      maintenance
      A minimal demonstration server showcasing MCP protocol capabilities including tools, resources, and prompts with basic examples like hello world functionality.
      1 npm
      MIT

    • MCP Minimal Agent Demo Server

      Synaptechlabs
      A
      license
      Not graded
      quality
      C
      maintenance
      A demo MCP server exposing three simple tools (get_github_activity, get_site_content, contact_scott) to illustrate tool discovery and invocation within an LLM agent harness using the Model Context Protocol.
      Creative Commons Zero v1.0 Universal

    • Basic MCP Server

      cyberimaginationsi-gif
      A
      license
      Not graded
      quality
      D
      maintenance
      A minimal template MCP server demonstrating basic tools, resources, and prompts functionality. Includes example implementations like a hello tool, history resource, and greet prompt for learning MCP development.
      1 npm
      ISC

    • containerized-mcp-streamable

      xavierxmorris
      F
      license
      Not graded
      quality
      C
      maintenance
      A minimal MCP server running in a container that connects to GitHub Copilot over stateless, JSON-only Streamable HTTP, exposing echo and server_info tools.
      -

    • mcp-current-repo

      Wolfe-Jam
      A
      license
      Not graded
      quality
      F
      maintenance
      A proof-of-concept MCP server that scopes GitHub tools to the current repository without filesystem access, using MCP roots to carry the repo identity.
      1
      MIT
    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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: repo info, listing issues, summarizing issues, and reading allowlisted files. There is no overlap or ambiguity among them.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern with camelCase (getRepoInfo, listOpenIssues, createIssueSummary), but safeFileRead deviates by placing an adjective before the object and putting the verb last. The mixed pattern is readable but inconsistent.

    Tool Count4/5

    Four tools is a reasonable number for a small lab server, not too sparse or bloated. However, the inclusion of safeFileRead alongside GitHub tools suggests a slightly unfocused scope, preventing a perfect score.

    Completeness3/5

    The GitHub-related tools cover read and summary operations for repos and open issues, but lack issue lifecycle actions like create, update, or close. safeFileRead appears unrelated to the primary domain, creating a notable gap in overall surface coherence.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources