io.github.detailobsessed/efficient-gitlab

MCPattested
v2.33.0io.github.detailobsessedUnknownUpdated 3mo agonpmGitHub

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

[](#available-categories) [](#available-categories) Token-efficient GitLab MCP server. A fork of zereight/gitlab-mcp re-architected for agent context budgets: 167 tools delivered through 3 meta-tools, with field projection on every list endpoint, server-side file trimming, and keyset pagination on large directories. If your agent's first turn against an MCP server costs ~20K tokens of tool…

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
3mo agoLast update
Package
Authorio.github.detailobsessed
LicenseUnknown
Version2.33.0
Sourcemcp-registry
Trust Status
A
85/100Trusted
Listed in Forge index+10/10
Identity verified · attested build+20/20
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+5/5
npm maintainer match+0/5
Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain
Provenance✓ Sigstore-verified · 06ab318
Dependencies60 resolved+ · none vulnerable
Tool surface
Security scan✓ Cleanv2.33.0 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

[](#available-categories) [](#available-categories) Token-efficient GitLab MCP server. A fork of zereight/gitlab-mcp re-architected for agent context budgets: 167 tools delivered through 3 meta-tools, with field projection on every list endpoint, server-side file trimming, and keyset pagination on large directories. If your agent's first turn against an MCP server costs ~20K tokens of tool definitions before you've asked anything, this fork is for you. A GitLab Personal Access Token with scope…

Keywords
mcp