Incidentoracle vs Git

A side-by-side look at the Incidentoracle and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Incidentoracle logoIncidentoracleSupport & Service ManagementIncidentOracle - 12-tool incident management MCP: triage, BaFin DORA reporting, RCA.36FairAuth: not declaredGit logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth required

Verdict: choose Incidentoracle for support & service management work; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Incidentoracle logoChoose Incidentoracle when

  • You need dedicated capabilities in the Support & Service Management domain.
  • You want tools like log_incident, classify_incident, major_incident_check.
Explore Incidentoracle

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIncidentoracle logoIncidentoracleGit logoGit
CategorySupport & Service ManagementVersion Control
Quality signal36/100 · Fair81/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars091,526
Directory activity 1 views 0 installs 0 upvotes 51 views 0 installs 0 upvotes
Tools1216

Tools & capabilities

Incidentoracle tools 12

  • log_incidentLog a new ICT-related incident. First step in the DORA incident management proce
  • classify_incidentClassify an incident against the 6 DORA criteria (RTS 2024/1772).
  • major_incident_checkQuick check: would these criteria values classify as a MAJOR incident?
  • initial_notificationGenerate the 4h initial notification for a MAJOR incident (ITS 2025/302 Annex I)
  • intermediate_reportGenerate the 72h intermediate report for a MAJOR incident (ITS 2025/302).
  • final_reportGenerate the 1-month final report with root cause analysis and lessons learned.
  • deadline_trackerTrack all active MAJOR incident reporting deadlines. Shows overdue and upcoming.
  • reclassifyReclassify an incident (MAJOR to NON-MAJOR or vice versa).
  • incident_statsDashboard: total/open/major incidents, overdue deadlines, by severity/status.
  • cyber_threat_notifyVoluntary notification of a significant cyber threat (Art. 19(2)).
  • incident_logFull incident register with filters (status, classification, severity, search).
  • health_checkServer status.

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Incidentoracle

No confirmed install command for Incidentoracle yet — follow the setup steps linked from its listing page rather than a guessed package name.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

Frequently asked questions

Incidentoracle is categorized under Support & Service Management and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Incidentoracle for support & service management work and Git for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Incidentoracle has no confirmed install command yet — follow its own setup instructions.

Incidentoracle has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add incidentoracle and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Incidentoracle has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars.