# io.github.detailobsessed/efficient-gitlab (npm · efficient-gitlab-mcp-server)

Token-efficient GitLab MCP: 167 tools via 3 meta-tools, field projection, keyset pagination

- Trust score: 68/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `efficient-gitlab-mcp-server`: 68/100 (this document), [markdown](https://verifymcp.io/servers/detailobsessed-efficient-gitlab/efficient-gitlab-mcp-server.md), [page](https://verifymcp.io/servers/detailobsessed-efficient-gitlab/efficient-gitlab-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `efficient-gitlab-mcp-server`
- Version: `2.33.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 96), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 96), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 79 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 219 tokens (~73/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add detailobsessed-efficient-gitlab -- npx -y efficient-gitlab-mcp-server
```

### Codex

```bash
codex mcp add detailobsessed-efficient-gitlab -- npx -y efficient-gitlab-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "detailobsessed-efficient-gitlab": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "efficient-gitlab-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add detailobsessed-efficient-gitlab --command npx --arg -y --arg efficient-gitlab-mcp-server
```

### Hermes

```yaml
mcp_servers:
  detailobsessed-efficient-gitlab:
    command: "npx"
    args: ["-y", "efficient-gitlab-mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "detailobsessed-efficient-gitlab": {
      "command": "npx",
      "args": [
        "-y",
        "efficient-gitlab-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +47)

- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Provenance: Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional] Licence: MIT

### 2026-08-01 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 28, +4)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-29 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (3)

### `list_categories` (~34 tokens)

List Tool Categories

List all available GitLab tool categories. Start here to discover what operations are available, then use activate_tools to enable a category.

### `activate_tools` (~84 tokens)

Activate Tool Category

Enable all tools in one or more categories. After activation, the tools will appear in your tool list automatically. Note: in Claude Code, freshly-activated tools become callable starting in the next turn, not the same turn that activated them — other clients may behave differently.

Input parameters:

- `categories` (array, required): Category names to activate (e.g., ['issues', 'merge-requests'])

### `deactivate_tools` (~101 tokens)

Deactivate Tool Category

Disable all tools in one or more categories. After deactivation, those tools are removed from the active set and stop appearing in tools/list. Useful for reclaiming context-window budget on long sessions when a category is no longer needed. Note: in Claude Code, the deactivated tools stop being callable starting in the next turn — other clients may behave differently.

Input parameters:

- `categories` (array, required): Category names to deactivate (e.g., ['issues', 'merge-requests'])

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/detailobsessed-efficient-gitlab/efficient-gitlab-mcp-server#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 21
- 2026-07-31: 28
- 2026-07-29: 24
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/efficient-gitlab-mcp-server
- Socket report: https://socket.dev/npm/package/efficient-gitlab-mcp-server
- Repository: https://github.com/detailobsessed/efficient-gitlab-mcp
- Changelog RSS feed: https://verifymcp.io/servers/detailobsessed-efficient-gitlab/efficient-gitlab-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/detailobsessed-efficient-gitlab/efficient-gitlab-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/detailobsessed-efficient-gitlab/efficient-gitlab-mcp-server