Scan MCP Online API Star

Gitlab Mr (npm) MCP Server

gitlab-mr-mcp npm v1.1.4

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.

[![GitHub stars](https://img.shields.io/github/stars/kevinlin/gitlab-mr-mcp?style=flat)](https://github.com/kevinlin/gitlab-mr-mcp/stargazers) [![License](https://img.shields.io/github/license/kevinlin/gitlab-mr-mcp)](LICENSE) [![smithery badge](https://s

View on npm ↗ Raw report (JSON) ↗
Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 10

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

  • add_merge_request_commentno sensitive capability
  • add_merge_request_diff_commentno sensitive capability
  • get_issue_detailsno sensitive capability
  • get_merge_request_commentsno sensitive capability
  • get_merge_request_detailsno sensitive capability
  • get_merge_request_diffno sensitive capability
  • get_projectsno sensitive capability
  • list_open_merge_requestsno sensitive capability
  • set_merge_request_descriptionno sensitive capability
  • set_merge_request_titleno sensitive capability

What this scan could not see

Versions 1

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
v1.1.4 latest A 98/100 0 1.13.0 2026-09-09

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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/gitlab-mr-mcp/badge.svg)](https://mcptrustchecker.com/registry/gitlab-mr-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/gitlab-mr-mcp"><img src="https://mcptrustchecker.com/registry/gitlab-mr-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/gitlab-mr-mcp/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 gitlab-mr-mcp --online

Use the free API → How scoring works

Other implementations of Gitlab Mr 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

Gitlab Mr (amirsina-mandegari) PyPI
A
gitlab-mr-mcp

Connect your AI assistant to GitLab via MCP

Developer Tools Score 99/100 1 finding Cap. Minimal

More in Developer Tools

1stay Source verified npm
A
1stay-mcp

Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.

Developer Tools Score 100/100 0 findings 17/wk Cap. Minimal
Adguard Home Source verified npm
A
@samik081/mcp-adguard-home

Manage AdGuard Home through AI assistants

Developer Tools Score 100/100 0 findings 243/wk Cap. Minimal
Ado Browser Source verified npm
A
mcp-ado-browser

Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.

Developer Tools Score 100/100 0 findings 21/wk Cap. Minimal
Adobe Experience Dev Source verified npm
A
@stubbedev/adobe-experience-dev-mcp

MCP server for Adobe Experience Manager Assets integration development

Developer Tools Score 100/100 0 findings 34/wk Cap. Minimal
Aemet Source verified npm
A
@rldona/aemet-mcp

Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.

Developer Tools Score 100/100 0 findings 17/wk Cap. Minimal
Affinity Mcp Bridge Source verified npm
A
affinity-mcp-bridge

A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.

Developer Tools Score 100/100 1 finding 73/wk Cap. Minimal