GitEasy MCP server
io.github.greenmtnsun/giteasygreenmtnsunstreamable-httpv1.6.2Scanned
Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.
22 tools: 1 can delete or cancel things, 1 do something that can't be undone, 11 change things and 9 only read.
- Reads private data · 9
- Reads text others write · 1
- Can send data out · 0
- 5 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the GitEasy MCP server can do
The GitEasy MCP server is published by the GitHub account greenmtnsun. It has 22 tools. It can delete or cancel things (1 tool: clear_junk), do things that cannot be undone, such as sending, paying or publishing (push) and create or change data (11 tools: set_vault, restore_file, reset_login, set_ssh and 7 more). 9 tools only read.
9 tools read private data (show_diagnostic, get_vault_status, show_releases and 6 more); 1 tool brings in text other people can write (search_history).
The fixed checks matched 5 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.6.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
22 tools
Deletes or cancels 1Claude Code: deny
clear_junkRemove untracked files and directories from the working tree (git clean -fd).No findings
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
Description, as the server wrote it Remove untracked files and directories from the working tree (git clean -fd). Returns list of removed paths.
Can't be undone 1Claude Code: ask
pushSend already-committed work to the remote without making a new commit.No findings
Why it is in this group
- The name "push" says "push": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it Send already-committed work to the remote without making a new commit. Pushes the current branch; on a branch's first push, sets the remote branch as its upstream automatically.
Changes things 11Claude Code: ask
new_releaseCreate an annotated git tag and push it to the remote.No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it Create an annotated git tag and push it to the remote. Returns the tag name and target commit SHA.
new_work_branchCreate a new branch from current HEAD and switch to it.No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it Create a new branch from current HEAD and switch to it. Returns branch name and base commit SHA.
reset_loginClear stored git credentials by unsetting the credential helper in local git config.1 finding
Why it is in this group
- The name "reset_login" says "reset": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Clear stored git credentials by unsetting the credential helper in l..."
Description, as the server wrote it Clear stored git credentials by unsetting the credential helper in local git config. Returns confirmation.
restore_fileRestore a single file to its HEAD state, discarding uncommitted changes.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Restore a single file to its HEAD state, discarding uncommitted changes. Returns restored file path.
save_workStage changes, commit with a message, and optionally push to remote.No findings
Why it is in this group
- The name "save_work" says "save": a word for a change.
Description, as the server wrote it Stage changes, commit with a message, and optionally push to remote. Returns commit SHA and push result.
set_sshChange a remote URL to its SSH equivalent.No findings
Why it is in this group
- The name "set_ssh" says "set": a word for a change.
Description, as the server wrote it Change a remote URL to its SSH equivalent. Returns old and new remote URLs.
set_tokenStore a personal access token for HTTP git authentication.No findings
Why it is in this group
- The name "set_token" says "set": a word for a change.
Description, as the server wrote it Store a personal access token for HTTP git authentication. Returns confirmation (token value is never echoed).
set_vaultConfigure the git credential helper to use a specific vault path.2 findings
Why it is in this group
- The name "set_vault" says "set": a word for a change.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Configure the git credential helper to use a specific vault path. Re..."
- Info
The input schema at properties.vaultPath.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.vaultPath.description: "Path to the credential helper vault executable."
Description, as the server wrote it Configure the git credential helper to use a specific vault path. Returns new credential helper value.
switch_workSwitch to an existing branch.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Switch to an existing branch. Returns the branch switched to and current HEAD SHA.
test_loginTest whether git credentials are working by attempting ls-remote against the origin.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Test whether git credentials are working by attempting ls-remote aga..."
Description, as the server wrote it Test whether git credentials are working by attempting ls-remote against the origin. Returns success/failure and remote refs count.
undo_changesDiscard uncommitted changes.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Discard uncommitted changes. If filePath given, restores that file; otherwise restores all tracked files. Returns list of restored paths.
Only reads 9Show 9 read-only tools
find_changesList changed files: staged, unstaged, and untracked.Reads private dataNo findings
Why it is in this group
- The name "find_changes" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "file": it reads files.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it List changed files: staged, unstaged, and untracked. Returns file counts and paths by status group.
get_updatesFetch from remote and show incoming commits not yet in local branch.Reads private dataNo findings
Why it is in this group
- The name "get_updates" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "commit": it reads repositories.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it Fetch from remote and show incoming commits not yet in local branch. Returns count and commit summaries.
get_vault_statusReport current git credential helper configuration.Reads private data1 finding
Why it is in this group
- The name "get_vault_status" says "get": a word for reading.
What it can reach
- private-dataThe name "get_vault_status" says "get" and "vault": it reads secrets.
- private-dataThe description's first sentence says "credential": it reads secrets.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Report current git credential helper configuration. Returns helper na..."
Description, as the server wrote it Report current git credential helper configuration. Returns helper name and scope.
search_historySearch commit history for commits whose message matches a search term.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_history" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "commit": it reads repositories.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
- untrusted-inputThe description's first sentence says "search" and "message": it reads messages, which other people can write.
Description, as the server wrote it Search commit history for commits whose message matches a search term. Returns matching commits with SHA, author, date, and message.
show_changeShow the diff for a specific file or all changed files.Reads private dataNo findings
Why it is in this group
- The name "show_change" says "show": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "file": it reads files.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it Show the diff for a specific file or all changed files. Returns unified diff text.
show_diagnosticShow git repository diagnostic info: current branch, upstream, HEAD SHA, remote URLs, and status summary.Reads private dataNo findings
Why it is in this group
- The name "show_diagnostic" says "show": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "repository": it reads repositories.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it Show git repository diagnostic info: current branch, upstream, HEAD SHA, remote URLs, and status summary.
show_historyShow recent commit history.Reads private dataNo findings
Why it is in this group
- The name "show_history" says "show": a word for reading.
What it can reach
- private-dataThe description's first sentence says "show" and "commit": it reads repositories.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it Show recent commit history. Returns commits with SHA, author, date, and message.
show_releasesList all tags/releases in the repository, newest first.Reads private dataNo findings
Why it is in this group
- The name "show_releases" says "show": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "repository": it reads repositories.
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it List all tags/releases in the repository, newest first. Returns tag names, target SHAs, and annotation messages.
show_remoteShow all remote names and their fetch/push URLs.Reads private dataNo findings
Why it is in this group
- The name "show_remote" says "show": a word for reading.
What it can reach
- private-dataThe input names a directory (input.workingDirectory), and the tool reads: it reads files.
Description, as the server wrote it Show all remote names and their fetch/push URLs. Returns list of remotes with URL and type.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data9
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 13
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 13 tools that change things (1 destructive, 1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://giteasy-mcp.azurewebsites.net/mcp: tools/list returned 22 tools to an anonymous client, including clear_junk (destructive), push (irreversible), set_vault (write), restore_file (write), reset_login (write) and 8 more
Findings
Matches of fixed checks, with the text they matched.
- Infoset_vault
The description mentions "credential".
What this check looks forMatched text
description: "Configure the git credential helper to use a specific vault path. Re..."
- Infoset_vault
The input schema at properties.vaultPath.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.vaultPath.description: "Path to the credential helper vault executable."
- Inforeset_login
The description mentions "credentials".
What this check looks forMatched text
description: "Clear stored git credentials by unsetting the credential helper in l..."
- Infoget_vault_status
The description mentions "credential".
What this check looks forMatched text
description: "Report current git credential helper configuration. Returns helper na..."
- Infotest_login
The description mentions "credentials".
What this check looks forMatched text
description: "Test whether git credentials are working by attempting ls-remote aga..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.6.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http giteasy https://giteasy-mcp.azurewebsites.net/mcp --header 'X-Api-Key: <your-x-api-key>'claude mcp add --transport http giteasy https://giteasy-mcp.azurewebsites.net/mcp --header 'X-Api-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__giteasy__show_diagnostic",
"mcp__giteasy__get_vault_status",
"mcp__giteasy__show_releases",
"mcp__giteasy__show_change",
"mcp__giteasy__find_changes",
"mcp__giteasy__show_remote",
"mcp__giteasy__get_updates",
"mcp__giteasy__search_history",
"mcp__giteasy__show_history"
],
"ask": [
"mcp__giteasy__push",
"mcp__giteasy__set_vault",
"mcp__giteasy__restore_file",
"mcp__giteasy__reset_login",
"mcp__giteasy__set_ssh",
"mcp__giteasy__save_work",
"mcp__giteasy__test_login",
"mcp__giteasy__new_release",
"mcp__giteasy__undo_changes",
"mcp__giteasy__switch_work",
"mcp__giteasy__new_work_branch",
"mcp__giteasy__set_token"
],
"deny": [
"mcp__giteasy__clear_junk"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as giteasy. Review it before you use it.
Capability tags behind 9 rules
- mcp__giteasy__show_diagnostic private-data
- mcp__giteasy__get_vault_status private-data
- mcp__giteasy__show_releases private-data
- mcp__giteasy__show_change private-data
- mcp__giteasy__find_changes private-data
- mcp__giteasy__show_remote private-data
- mcp__giteasy__get_updates private-data
- mcp__giteasy__search_history private-data, untrusted-input
- mcp__giteasy__show_history private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.greenmtnsun/giteasy/verify?hash=94c1ee7387da68ffd57f966699ef90267eafee4ea258071e1f56855383bfd4b5" | jq -e '.changed == false'Pinned hash 94c1ee7387da, from Nov 9, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.greenmtnsun/giteasy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.greenmtnsun/giteasy)Source: MCP Registry · repository. Synced Oct 25, 2026, 03:17 UTC.
GitEasy MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GitEasy MCP server safe?
- No scan can promise that. What its definitions show: 22 tools, 13 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the GitEasy MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: clear_junk.
Can the GitEasy MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: push.
What tools does the GitEasy MCP server have?
- 22 tools: 1 destructive, 1 irreversible, 11 write, 9 read. clear_junk, push, set_vault, restore_file, reset_login, set_ssh, save_work, test_login and 14 more.
Does the GitEasy MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the GitEasy MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the GitEasy MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.