Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/detailobsessed/efficient-gitlab-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/detailobsessed/efficient-gitlab-mcp/efficient-gitlab)<a href="https://agentmods.dev/mcp/detailobsessed/efficient-gitlab-mcp/efficient-gitlab"><img src="https://agentmods.dev/badge/mcp/detailobsessed/efficient-gitlab-mcp/efficient-gitlab/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/detailobsessed/efficient-gitlab-mcp/efficient-gitlab"><img src="https://agentmods.dev/badge/mcp/detailobsessed/efficient-gitlab-mcp/efficient-gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
efficient-gitlab scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"efficient-gitlab": {
"command": "npx",
"args": [
"-y",
"efficient-gitlab-mcp-server"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "",
"GITLAB_API_URL": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A f3e04d9cb1be
efficient-gitlab is an MCP server published in the GitHub repository detailobsessed/efficient-gitlab-mcp (3 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other mcp servers, from other repositories
gitlab-mcp-server
MCP server "gitlab-mcp-server" as configured in jmrplens/gitlab-mcp-server. Launched with https://github.com/jmrplens/gitlab-mcp-server/releases/download/v3.0.0/gitlab-mc. Needs 17 environment variables to run.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
glitchtip
MCP server "glitchtip", hosted remotely at glitchtip.infra.developerz.ai, as configured in developerz-ai/ai-task-master.
gitlab-mcp
MCP server (stdio) — proxy fino sobre a REST API v4 de um GitLab CE self-hosted, focado em navegar MRs e deixar review inline. Runs locally from the @vinihcrosa/gitlab-mcp npm package.
gitlab-mcp-server
MCP Server for GitLab API operations. Runs locally from the @therealchristhomas/gitlab-mcp-server npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.