Skip to main content
Glama
volqiii

gitverse-connector

by volqiii

Related Servers

Alternatives to gitverse-connector

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive local Codex on a target Git repository: inspect repo state, start and follow up on tasks, review events and diffs, and record audit evidence for research governance.
      27
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables self-hosted, read-only remote interaction with GitHub repositories, allowing listing repositories, searching code, and inspecting commits, pull requests, issues, and diffs via authenticated MCP clients.
      140 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables managing GitHub repositories, files, and user information through MCP, with support for creating, updating, and deleting repository contents, as well as fetching user profiles.
      1
      -

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlapping purposes. The tool's purpose is clearly defined as a status check.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (gitverse_connection_status), which is descriptive and consistent. There are no other tools to create inconsistency.

    Tool Count2/5

    One tool is too few for a server named 'gitverse-connector', which implies a broader scope of connection management. A single status check tool feels minimal and likely insufficient for real workflows.

    Completeness1/5

    The server only provides a status check with no connect, disconnect, or resource access operations. For a connector, this is severely incomplete and would leave agents unable to perform any actual connection tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues