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/structured-world/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/structured-world/gitlab-mcp/gitlab-mcp-gitlab-mcp)<a href="https://agentmods.dev/mcp/structured-world/gitlab-mcp/gitlab-mcp-gitlab-mcp"><img src="https://agentmods.dev/badge/mcp/structured-world/gitlab-mcp/gitlab-mcp-gitlab-mcp/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/structured-world/gitlab-mcp/gitlab-mcp-gitlab-mcp"><img src="https://agentmods.dev/badge/mcp/structured-world/gitlab-mcp/gitlab-mcp-gitlab-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gitlab-mcp 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-mcp": {
"command": "npx",
"args": [
"-y",
"@structured-world/gitlab-mcp"
],
"env": {
"GITLAB_TOKEN": "",
"GITLAB_API_URL": "",
"GITLAB_READ_ONLY_MODE": ""
}
}
}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 · 14 lines scan A 3e8185779c68
gitlab-mcp is an MCP server published in the GitHub repository structured-world/gitlab-mcp (8 stars, last pushed today), licensed Apache-2.0. 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
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
charlotte
Renders web pages into structured, agent-readable representations using headless Chromium. Runs locally from the @ticktockbent/charlotte npm package.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
filesystem-mcp
Secure filesystem MCP server for reading, writing, searching, diffing, and patching files. Runs locally from the @j0hanz/filesystem-mcp npm package. Needs 1 environment variable to run.
umt-npm-registry
Package metadata, search, and version tools for the npm registry. Runs locally from the @universal-mcp-toolkit/server-npm-registry npm package.
stochastic-thinking-mcp-server
MCP server "stochastic-thinking-mcp-server" as configured in chirag127/Stochastic-Thinking-MCP-Server. Runs locally from the stochastic-thinking-mcp-server npm package.