Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.detailobsessed/efficient-gitlab

NPM · EFFICIENT-GITLAB-MCP-SERVER · SCANNED AUG 3

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

Available components

npm · efficient-gitlab-mcp-server 68
+22 this week 68 Trust /100
Trust breakdown (6 categories)

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. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 96), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 96), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • 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. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 79 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 219 tokens (~73/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · efficient-gitlab-mcp-server

# add to Claude Code
claude mcp add detailobsessed-efficient-gitlab -- npx -y efficient-gitlab-mcp-server
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add detailobsessed-efficient-gitlab --command npx --arg -y --arg efficient-gitlab-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  detailobsessed-efficient-gitlab:
    command: "npx"
    args: ["-y", "efficient-gitlab-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "detailobsessed-efficient-gitlab": {
      "command": "npx",
      "args": [
        "-y",
        "efficient-gitlab-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +47
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • 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. security
    • Security disclosure: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.23 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • License: unverified → pass ▲ functional
    • Schema quality: unverified → good ▲ functional
    • Licence: MIT functional
  • 1 Aug 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 +4
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: unverified → 100 ▲ functional
  • 29 Jul 26 −22
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance metadata_mismatch

Ecosystem: npm · Outcome: metadata_mismatch

Reason: repo_metadata_mismatch

Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/detailobsessed/ci-components/.github/workflows/npm-publish-bun.yml@refs/heads/main
Rekor log index:
1549110242
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:87d4f5df21d7d54090b8f154b3bb695505f12754cd88d8521c6dd911af713b97ae7f9a28c538bbff5eb050bd52c9aa73ba03f037c17a862976f2f0916
Discovery method:
attestation_endpoint
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~219 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
activate_tools ~84

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.

NameTypeReqDescription
categoriesarrayyesCategory names to activate (e.g., ['issues', 'merge-requests'])

No output schema declared.

No examples provided.

deactivate_tools ~101

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.

NameTypeReqDescription
categoriesarrayyesCategory names to deactivate (e.g., ['issues', 'merge-requests'])

No output schema declared.

No examples provided.

list_categories ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.