Skip to main content
Glama
genoxdeveloper

@buygit/mcp-server

by genoxdeveloper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @buygit/mcp-server

No user-submitted related servers found.

    Related Servers

    • feldspar-scan

      project-feldspar-resources
      A
      license
      A
      quality
      A
      maintenance
      Free deterministic security scan of a public git repository (GitHub, GitLab, Codeberg, Bitbucket): vulnerable dependencies via OSV.dev, secret patterns, and config lint, returned as structured JSON. Tools: scan_repository(url), audit_pricing(). Runs locally over stdio (python3 web/mcp_stdio.py or the Dockerfile) and is also hosted at https://project-feldspar.com/mcp. MIT licence, stdlib-only. Buil
      2
      MIT

    • RepoCrunch

      kimwwk
      A
      license
      Not graded
      quality
      C
      maintenance
      Analyze GitHub repositories into structured JSON with tech stack detection, dependency analysis, health signals, and security checks. No AI, fully deterministic. Available as CLI and MCP server.
      9
      MIT

    • ossfind

      Aniket-kr1030
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.
      1,348 npm
      MIT

    • agentscore-mcp-server

      Thezenmonster
      A
      license
      A
      quality
      D
      maintenance
      MCP security trust layer. Continuously monitors 800+ MCP packages on npm for install scripts, command injection, hardcoded secrets, capability drift, and publisher posture. Ships a GitHub Action policy gate for PR-level allow/warn/block decisions. 5 MCP tools, no API key required.
      8
      78 npm
      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

    A4.3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools map to distinct workflow steps—search, trending, random, compare, audit, license check—so an agent can usually select correctly. Minor ambiguity exists between buygit_get_listing, buygit_explain, and buygit_deep_audit, and between search_tools and buygit_search, but descriptions clarify the boundaries.

    Naming Consistency4/5

    The buygit_ prefix and snake_case naming are consistent and readable. However, not all names follow a strict verb_noun pattern—trending, random, and stats are noun/adjective-style—and search_tools breaks the buygit_ prefix, creating a small inconsistency.

    Tool Count5/5

    14 tools sits within the well-scoped 3-15 range and each tool covers a distinct user intent or workflow phase. The set is broad but not bloated, with no obvious filler tools.

    Completeness5/5

    The server covers the full catalog lifecycle: discovery, search, detail, trending, random, comparison, alternatives, license compatibility, external auditing, deep auditing, and version diffs. There are no core dead ends, and optional gated features are clearly handled with fallback behavior.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources