io.github.detailobsessed/efficient-gitlab
NPM · EFFICIENT-GITLAB-MCP-SERVER
Token-efficient GitLab MCP: 167 tools via 3 meta-tools, field projection, keyset pagination
Available components
Last scanned (20 hours ago)
Scores higher than 96% of npm servers
Category Version Control
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to detailobsessed/efficient-gitlab-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 172 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 4 Nov 2026 · Analysed npm/efficient-gitlab-mcp-server@2.33.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | detailobsessed/efficient-gitlab-mcp |
| 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 | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:87d4f5df21d7d54090b8f154b3bb695505f12754cd88d8521c6dd911af713b97ae7f9a28c538bbff5eb050bd52c9aa73ba03f037c17a862976f2f0916 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
activate_tools Activate Tool Category ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | Category names to activate (e.g., ['issues', 'merge-requests']) |
No output schema declared.
No examples provided.
deactivate_tools Deactivate Tool Category ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | Category names to deactivate (e.g., ['issues', 'merge-requests']) |
No output schema declared.
No examples provided.
list_categories List Tool 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.
How do I install the io.github.detailobsessed/efficient-gitlab MCP server?
io.github.detailobsessed/efficient-gitlab runs locally as an npm package, launched with npx -y efficient-gitlab-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · efficient-gitlab-mcp-server
claude mcp add detailobsessed-efficient-gitlab -- npx -y efficient-gitlab-mcp-server
What is the io.github.detailobsessed/efficient-gitlab MCP server?
io.github.detailobsessed/efficient-gitlab is an MCP server listed in the public MCP registry as io.github.detailobsessed/efficient-gitlab. Token-efficient GitLab MCP: 167 tools via 3 meta-tools, field projection, keyset pagination. This page covers its npm package (efficient-gitlab-mcp-server).
Is the io.github.detailobsessed/efficient-gitlab MCP server safe to use?
io.github.detailobsessed/efficient-gitlab scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.detailobsessed/efficient-gitlab MCP server expose?
io.github.detailobsessed/efficient-gitlab exposes 3 tools: list_categories, activate_tools, deactivate_tools. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.
Is the io.github.detailobsessed/efficient-gitlab MCP server still maintained?
io.github.detailobsessed/efficient-gitlab is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.detailobsessed/efficient-gitlab MCP server under?
io.github.detailobsessed/efficient-gitlab declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.