Gitlab Crunchtools MCP Server

mcp-gitlab-crunchtools PyPI v0.4.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
90/100
Last scanned
Trust
A · 90/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 98 − adoption risk = 90/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 2.1 = 98. What the published surface and source actually contain:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

2. Client adoption risk — 98 − 8 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−5 publisher verification (unlocatable) — no provenance and no public repository to inspect
inspection depth (source) — how much of the target the scan could see

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

medium Tool "create_file_tool" can modify the filesystemMTC-CAP-002

Tool "create_file_tool" can write, overwrite or delete files (keyword "create_file"). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool create_file_tool

low Mutating tool "create_file_tool" declares no destructiveHintMTC-CAP-005

Tool "create_file_tool" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool create_file_tool

low Package has no source repositoryMTC-SUP-011

"mcp-gitlab-crunchtools" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package mcp-gitlab-crunchtools

Tools 63

Each tool and what it can reach — statically extracted from the published source.

  • create_file_toolwrites files
  • create_issue_note_toolnetwork egress
  • create_issue_toolnetwork egress
  • cancel_job_toolno sensitive capability
  • cancel_pipeline_toolno sensitive capability
  • compare_branches_toolno sensitive capability
  • create_branch_toolno sensitive capability
  • create_label_toolno sensitive capability
  • create_merge_request_toolno sensitive capability
  • create_milestone_toolno sensitive capability
  • create_mr_discussion_toolno sensitive capability
  • create_mr_note_toolno sensitive capability
  • create_pipeline_toolno sensitive capability
  • create_project_toolno sensitive capability
  • create_release_toolno sensitive capability
  • create_snippet_toolno sensitive capability
  • create_wiki_page_toolno sensitive capability
  • delete_branch_toolno sensitive capability
  • delete_job_toolno sensitive capability
  • delete_label_toolno sensitive capability
  • delete_pipeline_toolno sensitive capability
  • delete_project_toolno sensitive capability
  • get_current_user_toolno sensitive capability
  • get_file_toolno sensitive capability
  • get_group_toolno sensitive capability
  • get_issue_toolno sensitive capability
  • get_job_log_toolno sensitive capability
  • get_merge_request_toolno sensitive capability
  • get_mr_changes_toolno sensitive capability
  • get_pipeline_toolno sensitive capability
  • get_project_branch_toolno sensitive capability
  • get_project_toolno sensitive capability
  • get_release_toolno sensitive capability
  • get_user_toolno sensitive capability
  • get_wiki_page_toolno sensitive capability
  • list_group_projects_toolno sensitive capability
  • list_groups_toolno sensitive capability
  • list_issue_notes_toolno sensitive capability
  • list_issues_toolno sensitive capability
  • list_labels_toolno sensitive capability
  • list_merge_requests_toolno sensitive capability
  • list_milestones_toolno sensitive capability
  • list_mr_discussions_toolno sensitive capability
  • list_mr_notes_toolno sensitive capability
  • list_pipeline_jobs_toolno sensitive capability
  • list_pipelines_toolno sensitive capability
  • list_project_branches_toolno sensitive capability
  • list_project_commits_toolno sensitive capability
  • list_projects_toolno sensitive capability
  • list_releases_toolno sensitive capability
  • list_repository_tree_toolno sensitive capability
  • list_snippets_toolno sensitive capability
  • list_users_toolno sensitive capability
  • list_wiki_pages_toolno sensitive capability
  • retry_job_toolno sensitive capability
  • retry_pipeline_toolno sensitive capability
  • search_global_toolno sensitive capability
  • search_project_toolno sensitive capability
  • update_file_toolno sensitive capability
  • update_issue_toolno sensitive capability
  • update_label_toolno sensitive capability
  • update_merge_request_toolno sensitive capability
  • update_milestone_toolno sensitive capability

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.4.1 latest A 90/100 3 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 90/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-gitlab-crunchtools/badge.svg)](https://mcptrustchecker.com/registry/mcp-gitlab-crunchtools)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-gitlab-crunchtools"><img src="https://mcptrustchecker.com/registry/mcp-gitlab-crunchtools/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-gitlab-crunchtools/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-gitlab-crunchtools --online --registry pypi

Use the free API → How scoring works

More in Developer Tools