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/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/gitlab)<a href="https://agentmods.dev/mcp/viknesh20-20/claude-code-tool-kit/gitlab"><img src="https://agentmods.dev/badge/mcp/viknesh20-20/claude-code-tool-kit/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/viknesh20-20/claude-code-tool-kit/gitlab"><img src="https://agentmods.dev/badge/mcp/viknesh20-20/claude-code-tool-kit/gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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
{
"gitlab": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "${GITLAB_PERSONAL_ACCESS_TOKEN}",
"GITLAB_API_URL": "${GITLAB_API_URL}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 45. Installing the file brings all of them; each is measured and scanned on its own page.
- MCP server aws A not measured
- MCP server brave-search A not measured
- MCP server browserbase A not measured
- MCP server chroma A not measured
- MCP server claude-context A not measured
- MCP server cloudflare A not measured
- MCP server context7 A not measured
- MCP server datadog A not measured
- MCP server e2b A not measured
- MCP server elevenlabs A not measured
- MCP server exa A not measured
- MCP server fetch A not measured
- MCP server figma A not measured
- MCP server filesystem A not measured
- MCP server firecrawl A not measured
- MCP server github A not measured
- MCP server grafana A not measured
- MCP server huggingface A not measured
- MCP server kubernetes A not measured
- MCP server linear A not measured
- MCP server magic A not measured
- MCP server memory A not measured
- MCP server mongodb A not measured
- MCP server netlify A not measured
- MCP server notion A not measured
- MCP server perplexity A not measured
- MCP server playwright A not measured
- MCP server postgres A not measured
- MCP server puppeteer A not measured
- MCP server qdrant A not measured
- MCP server redis A not measured
- MCP server replicate A not measured
- MCP server sentry A not measured
- MCP server sequential-thinking A not measured
- MCP server serena A not measured
- MCP server slack A not measured
- MCP server snyk A not measured
- MCP server sonarqube A not measured
- MCP server sqlite A not measured
- MCP server stripe A not measured
- MCP server supabase A not measured
- MCP server tavily A not measured
- MCP server twilio A not measured
- MCP server vercel A not measured
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 ea7bbfc91f25
gitlab is an MCP server published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
atlassian-mcp
MCP server for self-hosted Jira and Bitbucket (Go, distributed as a prebuilt binary). Runs locally from the @stubbedev/atlassian-mcp npm package.
keelen
MCP server "keelen", hosted remotely at keelen.ai, as configured in jamie7893/keelen-mcp.
gitlab
GitLab MCP — wraps the GitLab REST API v4 (BYO API key). Remote server at gateway.pipeworx.io.
gitlab
Secure MCP server for GitLab projects, merge requests, issues, and pipelines. Runs locally from the mcp-gitlab-crunchtools Python package.
gitlab-nexus
MCP server "gitlab-nexus" as configured in rajkumar-madhu/mcp. Runs gitlab_nexus_mcp.py with python. Needs 2 environment variables to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.