Skip to main content
Glama

Related Servers

Alternatives to reposniffer-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover GitHub repositories by expanding intents into multiple keyword queries, searching GitHub's live Search API, and returning deduplicated, ranked candidates with README excerpts and metadata.
      1
      10 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.
      4
      174 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and retrieve context from GitHub issues, pull requests, releases, and documentation using hybrid semantic search and time-ordered activity scans.
      24 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Discover, rank, and compare GitHub repositories from any MCP-compatible AI client. Enables searching, filtering, ranking, and evaluating open-source repositories by topic, language, stars, license, activity, and relevance.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A production-grade GitHub repository finder that helps LLMs discover best repositories with advanced search, ranking, and token optimization.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to semantically search and navigate code repositories using natural language, with support for multiple repos, incremental indexing, and no local install needed.
      -

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    find_repos is clearly for discovering projects by feature, repo_intel is clearly for validating an already-known repo, and health is an operational diagnostic. The purposes are distinct and the descriptions reinforce the boundaries.

    Naming Consistency3/5

    The names are readable and unambiguous, but they do not follow a single pattern: find_repos uses verb_noun, while repo_intel and health are noun-style labels. There is no chaotic mixing of casing, but the conventions are inconsistent.

    Tool Count5/5

    Three tools is an appropriate size for a focused repo-intelligence server. Each tool has a clear role: discovery, verification, and service health, so none feels redundant or extraneous.

    Completeness4/5

    The core workflow is covered: discover candidate repos, validate them for adoption, and check service health. A minor gap is the lack of a dedicated detailed-comparison tool, but the combination of verdicts and alternatives in repo_intel makes the surface functional.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive