GitEasy MCP
REMOTE · GITEASY-MCP.AZUREWEBSITES.NET
Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.
Available components
Last scanned (9 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Version Control
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 22 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability91
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1329 tokens (~60/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_junk" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Server version: 1.6.0.0 → 1.6.1.0 functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://giteasy-mcp.azurewebsites.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azurewebsites.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US | 3 Oct 2026 | 19 Apr 2027 | RSA 2048 | SHA384-RSA | 49011ec5b2c96705cda30d8b680000011ec5b2 |
| SANs: *.azurewebsites.net, *.scm.azurewebsites.net, *.sso.azurewebsites.net, *.westus2-01.azurewebsites.net, *.scm.westus2-01.azurewebsites.net, *.sso.westus2-01.azurewebsites.net, *.westus2.c.azurewebsites.net, *.scm.westus2.c.azurewebsites.net, *.sso.westus2.c.azurewebsites.net, *.02.westus2.c.azurewebsites.net, *.scm.02.westus2.c.azurewebsites.net, *.sso.02.westus2.c.azurewebsites.net and 18 more | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000f33206537ee42ae4f00000000000f |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of giteasy-mcp.azurewebsites.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| azurewebsites.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://giteasy-mcp.azurewebsites.net/mcp | Verified | 200 | |
| http (plaintext) | http://giteasy-mcp.azurewebsites.net/mcp | Inconclusive | 401 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
clear_junk ~46
Remove untracked files and directories from the working tree (git clean -fd). Returns list of removed paths.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
find_changes ~45
List changed files: staged, unstaged, and untracked. Returns file counts and paths by status group.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
get_updates ~55
Fetch from remote and show incoming commits not yet in local branch. Returns count and commit summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| remoteName | string | – | Remote name. Default origin. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
get_vault_status ~38
Report current git credential helper configuration. Returns helper name and scope.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
new_release ~91
Create an annotated git tag and push it to the remote. Returns the tag name and target commit SHA.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Annotation message for the tag. |
| remoteName | string | – | Remote to push to. Default origin. |
| tagName | string | – | Tag name, e.g. v1.2.0. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
new_work_branch ~57
Create a new branch from current HEAD and switch to it. Returns branch name and base commit SHA.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | Name of the new branch. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
push ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| remoteName | string | – | Remote name. Default origin. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
reset_login ~41
Clear stored git credentials by unsetting the credential helper in local git config. Returns confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
restore_file ~60
Restore a single file to its HEAD state, discarding uncommitted changes. Returns restored file path.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | Repo-relative path to the file to restore. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
save_work ~89
Stage changes, commit with a message, and optionally push to remote. Returns commit SHA and push result.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array|null | – | Files to commit. Default empty (commits all changes). |
| message | string | – | Commit message. |
| pushToRemote | boolean | – | Push to remote after commit. Default false. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
search_history ~78
Search commit history for commits whose message matches a search term. Returns matching commits with SHA, author, date, and message.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max commits to return. Default 20. |
| searchTerm | string | – | Text to search for in commit messages. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
set_ssh ~80
Change a remote URL to its SSH equivalent. Returns old and new remote URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| remoteName | string | – | Remote name to update. Default origin. |
| sshUrl | string | – | New SSH remote URL, e.g. git@github.com:owner/repo.git. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
set_token ~54
Store a personal access token for HTTP git authentication. Returns confirmation (token value is never echoed).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Personal access token to store. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
set_vault ~57
Configure the git credential helper to use a specific vault path. Returns new credential helper value.
| Name | Type | Req | Description |
|---|---|---|---|
| vaultPath | string | – | Path to the credential helper vault executable. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
show_change ~71
Show the diff for a specific file or all changed files. Returns unified diff text.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | Repo-relative file path. If empty, shows all. |
| staged | boolean | – | Show staged diff. Default false. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
show_diagnostic ~45
Show git repository diagnostic info: current branch, upstream, HEAD SHA, remote URLs, and status summary.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
show_history ~70
Show recent commit history. Returns commits with SHA, author, date, and message.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | Branch name. Default current branch. |
| limit | integer | – | Number of commits to return. Default 20. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
show_releases ~47
List all tags/releases in the repository, newest first. Returns tag names, target SHAs, and annotation messages.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
show_remote ~44
Show all remote names and their fetch/push URLs. Returns list of remotes with URL and type.
| Name | Type | Req | Description |
|---|---|---|---|
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
switch_work ~54
Switch to an existing branch. Returns the branch switched to and current HEAD SHA.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | – | Name of the branch to switch to. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
test_login ~61
Test whether git credentials are working by attempting ls-remote against the origin. Returns success/failure and remote refs count.
| Name | Type | Req | Description |
|---|---|---|---|
| remoteName | string | – | Remote to test. Default origin. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
undo_changes ~74
Discard uncommitted changes. If filePath given, restores that file; otherwise restores all tracked files. Returns list of restored paths.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | Repo-relative file path to undo. If empty, undoes all tracked changes. |
| workingDirectory | string | – | Git repo path. Default current directory. |
No output schema declared.
No examples provided.
How do I install the GitEasy MCP server?
GitEasy MCP is a hosted endpoint at https://giteasy-mcp.azurewebsites.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · giteasy-mcp.azurewebsites.net
claude mcp add --transport http greenmtnsun-giteasy 'https://giteasy-mcp.azurewebsites.net/mcp'
What is the GitEasy MCP server?
GitEasy MCP is listed in the public MCP registry as io.github.greenmtnsun/giteasy. Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier. This page covers its hosted endpoint (https://giteasy-mcp.azurewebsites.net/mcp).
Is the GitEasy MCP server safe to use?
GitEasy MCP scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GitEasy MCP server expose?
GitEasy MCP exposes 22 tools: push, show_diagnostic, set_vault, restore_file, reset_login, and 17 more. Their descriptions and schemas cost roughly 1,329 tokens of context every time the server is loaded.
Does the GitEasy MCP server require authentication?
No. We connected to GitEasy MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GitEasy MCP server still maintained?
GitEasy MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.