Skip to main content
Glama
dmmulroy

opensrc-mcp

by dmmulroy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to opensrc-mcp

No user-submitted related servers found.

    Related Servers

    • GitHits by githits-com

      GitHitsofficial

      githits-com
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.
      1,996 npm
      113
      Apache 2.0

    • ContextCache MCP

      pandolfipedro
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that indexes TypeScript/JavaScript projects and returns budget-aware, dependency-optimized context packs for AI coding assistants.
      1
      MIT

    • voyager

      dir-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables coding agents to safely verify npm/PyPI packages, retrieve cited briefs, discover GitHub repos, and fetch canonical docs, with fail-closed OSV vulnerability checks and injection-hardened output.
      117 npm
      MIT

    • Satori

      ham-zax
      A
      license
      Not graded
      quality
      B
      maintenance
      Agent-safe code retrieval MCP server that indexes repositories and provides semantic search, file navigation, call graph analysis, and bounded file reading tools for coding agents.
      2,693,148 npm
      3
      AGPL 3.0

    • Semdex

      raghavwahi
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that parses codebases into semantic chunks, indexes them in SQLite with vector embeddings, and exposes MCP tools for LLM agents to query.
      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.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The single tool encompasses a well-defined API, and its purpose is clearly described in the description.

    Naming Consistency5/5

    The server has a single tool named 'execute', which is consistent in itself. While the name is generic, there are no other tools to compare against, so no naming inconsistencies exist.

    Tool Count2/5

    The domain covers fetching, searching, reading, and managing source code from multiple ecosystems, which is a broad scope. Exposing all of this through a single monolithic tool is overly condensed; separate tools for distinct operations (e.g., fetch, read, grep) would be more appropriate for agent discoverability.

    Completeness4/5

    The tool covers listing, fetching, reading, searching (grep and astGrep), and removal of sources, which is comprehensive for exploration. However, it lacks explicit update/edit capabilities for source files and no direct way to modify code, leaving a minor gap in mutation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources