Skip to main content
Glama
nixkeeper-mcp
by nixkeeper

Related Servers

Alternatives to nixkeeper-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to access modular system, Nix flake, and repository diagnostic tools over strict stdio JSON-RPC, including host metadata, project manifest inspection, and Git/Nix environment health checks.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to query a local code graph over stdio, so they can see what a Git change may affect, find related tests, routes and nodes, and cite evidence paths — read-only and fully on-machine.
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes code-review and issue-triage tools to AI assistants over stdio, letting them evaluate unified pull-request diffs for maintainer remarks, slice diffs into categorized AST hunks, and classify GitHub issues by priority while synthesizing minimal reproduction stubs.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI assistant to retrieve IT system status and search or rebuild a vector-indexed knowledge base of operational runbooks. It supports local, tool-grounded responses over stdio for Ollama-based agents, helping prevent hallucinated IT operations guidance.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Access the Nix ecosystem (Nixpkgs, NixOS, Home Manager, nix-darwin, nixvim, nixhub...)
      7
      GPL 3.0

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly different resources or actions: find_packages searches, package retrieves one package, issues and pull_requests cover distinct artifact types, and vulnerabilities and update_attempts are specialized. There is some conceptual overlap among overview, needs_attention, and build_failures because all surface problematic packages/builds, but the detailed descriptions mostly make the boundaries usable.

    Naming Consistency3/5

    All names use snake_case, but the convention is mixed: find_packages is verb_noun while package, overview, issues, vulnerabilities, pull_requests, build_failures, needs_attention, data_status, and update_attempts are noun/resource phrases. Singular/plural usage also varies (package vs issues/pull_requests), so the pattern is readable but not strongly predictable.

    Tool Count5/5

    Ten tools is well within a reasonable range and fits the server's monitoring scope. Each tool covers a distinct area of nixpkgs health: package lookup/detail, build failures, dashboard summaries, issues, PRs, vulnerabilities, update-bot attempts, and data freshness.

    Completeness4/5

    The surface covers the main read-only monitoring lifecycle: package discovery and detail, aggregate health, attention lists, build failures, issues, PRs, CVEs/advisories, update attempts, and digest freshness. Minor gaps exist around deeper direct issue/PR detail or explicit maintainer/team listing, but core workflows appear covered.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing