Skip to main content
Glama

GH-600 MCP Server Lab

A runnable Model Context Protocol server, by Certy. Maps to GH-600 domain 2.0 - Tooling, MCP Servers & Execution Context.

Deterministic and local: the tools use fake in-memory data, so the server runs with no network and no tokens.

Run it

npm install
npm test            # 7 tool/security tests
npm run typecheck
npm start           # starts the MCP server over stdio

Connect a host with mcp-config.example.json (runs npx tsx src/index.ts).

Related MCP server: Basic MCP Server

What is here

  • src/index.ts - a real MCP server (using @modelcontextprotocol/sdk) that registers four tools and one resource.

  • src/tools/ - pure tool functions (getRepoInfo, listOpenIssues, createIssueSummary, safeFileRead).

  • src/security/ - an allowlist and a rate limiter.

  • src/resources/repoContext.ts - a read-only MCP resource.

  • docs/ - MCP overview, tool registration, stdio vs SSE, execution context.

Licence

MIT.

Available Tools

4 tools
createIssueSummaryC

Summarise a repository's open issues.

Inputs: repo (required).

getRepoInfoC

Get basic information about a repository.

Inputs: repo (required).

listOpenIssuesB

List the open issues for a repository.

Inputs: repo (required).

safeFileReadB

Read an allowlisted file safely.

Inputs: path (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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.
      MIT
    • 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.
      ISC
    • A
      license
      Not graded
      quality
      D
      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.
      1
      Creative Commons Zero v1.0 Universal