Git MCP Assistant Tool (kamiwaza-drew/tool-git) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

Git MCP Assistant Tool

Enables AI models to perform comprehensive Git repository management including cloning, file operations, branching, committing, and pushing changes via a secure FastMCP interface. It features built-in workspace isolation and rigorous input validation to ensure production-ready repository control.

→ kamiwaza-drew/tool-git· listed on glama

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

Code 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

kamiwaza-drew

Source: Glama

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

Glamanot scored here

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
🚨
Secret credentials may flow to a network call
2 flows detected: KAMIWAZA_PUBLIC_API_URL. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: KAMIWAZA_API_KEY, KAMIWAZA_API_TOKEN, KAMIWAZA_PASSWORD, AUTH_GATEWAY_STATE_SECRET, FORWARDAUTH_SIGNATURE_SECRET
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.
configBACKEND_URL
🔐 secretKAMIWAZA_API_KEY
🔐 secretKAMIWAZA_API_TOKEN
configKAMIWAZA_API_URL
configKAMIWAZA_BASE_URL
configKAMIWAZA_PUBLIC_API_URL
configGIT_WORKSPACE_ROOT
configREPO_VERSION
configSTAGE
configKAMIWAZA_REMOTE_TEMPLATE_BASE_URL
configKAMIWAZA_REMOTE_TEMPLATE_APPS_PATH
configKAMIWAZA_REMOTE_TEMPLATE_TOOLS_PATH
configKAMIWAZA_USERNAME
🔐 secretKAMIWAZA_PASSWORD
configAWS_PROFILE
configKAMIWAZA_REGISTRY_ENDPOINT
configKAMIWAZA_REGISTRY_ACCOUNT_ID
configKAMIWAZA_REGISTRY_BUCKET
configKAMIWAZA_REGISTRY_REGION
configKAMIWAZA_REGISTRY_LOCK_NAME
configGITHUB_RUN_ID
configKAMIWAZA_ENDPOINT
configAUTH_VALIDATE_URL
configKAMIWAZA_USE_AUTH
🔐 secretAUTH_GATEWAY_STATE_SECRET
🔐 secretFORWARDAUTH_SIGNATURE_SECRET
configKAMIWAZA_TLS_REJECT_UNAUTHORIZED
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_API_BASE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

13/13 tools missing one or more hints — clone_repository (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); write_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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 handlers catch errors

Only 0/13 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

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 5 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/kamiwaza-drew/tool-git)](https://m8ven.ai/mcp/kamiwaza-drew/tool-git)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 34ab64322c6ba6b503a8f55b0aeaf89f3fcf4143
code hash: 5ac677f01d0b57ead8fa3eb203f2c635abc2b065a8b2fc2f15fc1cf7d36dc1ac
verified: 8/6/2026, 3:08:56 PM
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