Home / MCP registry index / io.github.greenmtnsun/giteasy
io.github.greenmtnsun/giteasy
io.github.greenmtnsun/giteasy in the official MCP registry.
Endpoint https://giteasy-mcp.azurewebsites.net/mcp. Source: github.com/greenmtnsun/GitEasy-internal.
The registry describes it as: Plain-English git via MCP: 22 tools to branch, commit, push, and tag. No git jargon.
We read its 22 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
push show_diagnostic set_vault restore_file reset_login set_ssh save_work get_vault_status test_login show_releases show_change new_release find_changes show_remote get_updates undo_changes switch_work search_history show_history new_work_branch set_token clear_junk
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-greenmtnsun-giteasy)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.