ttpears/gitlab-mcp (ttpears/gitlab-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 63 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
7 days ago

ttpears/gitlab-mcp

GitLab MCP Server with GraphQL discovery

→ ttpears/gitlab-mcp· npm: @ttpears/gitlab-mcp-server0· listed on smithery

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ttpears

Source: Smithery · also listed on npm

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Smitherynot scored herenpmscored separately

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: GITLAB_OAUTH_CLIENT_SECRET, GITLAB_READ_TOKEN, GITLAB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGITLAB_ALLOW_SHARED_ESCAPE_HATCHfalse
configGITLAB_ANALYTICS_MAX_PROJECTS500
configGITLAB_MAX_CONCURRENCYMax concurrent in-flight requests to GitLab (excess queue, never rejected). 0 = unlimited 16
configGITLAB_MAX_PAGE_SIZEMaximum items per page (1–100) 50
configGITLAB_MCP_OAUTHfalse
configGITLAB_MCP_PORT8008
configGITLAB_OAUTH_ALLOWED_GROUPSunset
configGITLAB_OAUTH_CALLBACK_PATH/gitlab/callback
configGITLAB_OAUTH_CLIENT_IDGitLab application id — required when OAuth is on —
🔐 secretGITLAB_OAUTH_CLIENT_SECRETGitLab application secret (omit for a public/PKCE-only app) —
configGITLAB_OAUTH_SCOPESapi
configGITLAB_PIN_HOSTtrue
🔐 secretGITLAB_READ_TOKENenv_file reads GITLAB_URL and from .env. No port
configGITLAB_TIMEOUT30000
🔐 secretGITLAB_TOKENEach contributor exports in their shell; Claude Code expands it on launch.
configGITLAB_URLenv_file reads and GITLAB_READ_TOKEN from .env. No port
configMCP_SERVER_URLmust be HTTPS (terminate TLS at your reverse proxy) and must
configMCP_TRANSPORTstdio
configREDIS_KEY_PREFIXgitlab-mcp
configTRUST_PROXYunset
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
// quality suggestions

All four hints declared on every tool

63/63 tools missing one or more hints — get_current_user (missing: openWorldHint); get_project (missing: openWorldHint); get_projects (missing: openWorldHint), +60 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 5/63 tools referenced in tests (8%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not logged

2 secret values sent to error

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/ttpears/gitlab-mcp)](https://m8ven.ai/mcp/ttpears/gitlab-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 88e36b72a60c92037f78e509c4f8caea07f41eca
code hash: 007e7280fba512533d6b84048ca402d69cf39eea20d25c4a044bb524ad5be89d
verified: 9/5/2026, 7:19:00 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client