Is the Greenmtnsun Giteasy MCP server down?

mcp-registry/io.github.greenmtnsun/giteasy · v1.6.1.0

healthy
Last checked 2026-10-26 17:13 UTC · handshake 116ms

As of 2026-10-26 17:13 UTC, the Greenmtnsun Giteasy MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
4,888
outages (90d)
4
tools
22

Plain-English git via MCP: 22 tools to branch, commit, push, and tag. No git jargon.

Point your MCP client at this streamable-http endpoint: https://giteasy-mcp.azurewebsites.net/mcp

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 22 tool(s); ~2,483 tokens of tool definitions.
Scores higher than 36% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~2,483 tokens per session — more than 50% of servers.
80 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints9
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

22 of 22 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: clear_junk, find_changes, get_updates, get_vault_status, new_release and 17 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: set_ssh, set_token, set_vault

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 13 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy/fixes

find_changes 1 change 
{
  "name": "find_changes",
  "description": "List changed files: staged, unstaged, and untracked. Returns file counts and paths by status group.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "workingDirectory": {
        "type": "string",
        "default": ".",
        "description": "Git repo path. Default current directory."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_updates 1 change 
{
  "name": "get_updates",
  "description": "Fetch from remote and show incoming commits not yet in local branch. Returns count and commit summaries.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "remoteName": {
        "type": "string",
        "default": "origin",
        "description": "Remote name. Default origin."
      },
      "workingDirectory": {
        "type": "string",
        "default": ".",
        "description": "Git repo path. Default current directory."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_vault_status 1 change 
{
  "name": "get_vault_status",
  "description": "Report current git credential helper configuration. Returns helper name and scope.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "workingDirectory": {
        "type": "string",
        "default": ".",
        "description": "Git repo path. Default current directory."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.greenmtnsun/giteasy"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.greenmtnsun/giteasy"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy.svg)](https://glimind.com/server/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.greenmtnsun%2Fgiteasy?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:28ca59cc9365b4ac…, first seen 2026-10-17, included at leaf 5056 of 74,339. Version history · verify what your client received.

Tools (22)

Compare: most reliable files servers · most reliable code servers · most reliable devops servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Greenmtnsun Giteasy MCP server down right now?

As of 2026-10-26 17:13 UTC, the Greenmtnsun Giteasy MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Greenmtnsun Giteasy MCP server provide?

Greenmtnsun Giteasy MCP server advertises 22 tools, including clear_junk, find_changes, get_updates, get_vault_status, new_release.

How do I install Greenmtnsun Giteasy MCP server?

Point your MCP client at this streamable-http endpoint: https://giteasy-mcp.azurewebsites.net/mcp

Is the Greenmtnsun Giteasy MCP server safe to connect to an AI agent?

Glimind scanned all 22 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Greenmtnsun Giteasy MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve