SERVER

IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow

Rank #161,944

smithery/tofan96you/incidentforge-mcp

Structured security incident response workflow for engineering, security, operations and B2B teams. Build a timestamped evidence-aware incident timeline; assess affected systems, users, downtime and data types; classify severity using explicit confirmed-impact criteria; create containment, evidence-preservation, recovery and closeout plans; draft internal, customer and executive communications that separate confirmed facts from investigation items; and generate a blameless postmortem with root-cause analysis, lessons and corrective actions with owners and deadlines. The workflow distinguishes Confirmed, Likely, Unknown and Needs Investigation instead of fabricating breach details or compliance conclusions. No API key required. Free tier: 10 requests/day. Operational triage only; obtain qualified legal and privacy advice for notification decisions.

Versions unknown

First listed

Oct 11, 2026

Last publish date

—

PURPOSE

What you can do with IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow

IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow is a Model Context Protocol (MCP) server. It ranks #161,944 of 162,202 active servers on MCP Toplist. IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow is listed on Smithery; no version information is available from the registries that list it or from its repository. It was first listed on Oct 11, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. Its registry listings below are the authority on what it does.

CAPABILITIES AND LIMITATIONS

What IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow can and cannot do

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. Check its registry listings below.

REQUIREMENTS

What you need before using IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow

DeclaredRemote authHosted remote, sign-in declared

The hosted endpoint is declared as gated by authentication — connect via its URL and authenticate with the provider (OAuth flow or an API key/header, per its docs).

Declared by Smithery, last synced Oct 28, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

Hosted endpoint declared as requiring authentication.

INSTALLATION AND FIRST TASK

Connect IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow and confirm it works

Remote · HTTP

claude mcp add --transport http incidentforge-mcp https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp

This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

[mcp_servers.incidentforge-mcp]
url = "https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp"

Add to ~/.codex/config.toml. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp

Settings → Connectors → “Add custom connector”, then paste this URL. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "incidentforge-mcp": {
      "url": "https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp"
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "servers": {
    "incidentforge-mcp": {
      "type": "http",
      "url": "https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp"
    }
  }
}

Save as .vscode/mcp.json in your workspace. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "incidentforge-mcp": {
      "serverUrl": "https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. This endpoint requires authentication — see the server’s docs for credentials.

Remote · HTTP

{
  "mcpServers": {
    "incidentforge-mcp": {
      "url": "https://server.smithery.ai/tofan96you/incidentforge-mcp/mcp"
    }
  }
}

This endpoint requires authentication — see the server’s docs for credentials.

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: Oct 11, 2026
Version history: Unavailable — no registry exposes versions and no release tags were found
Requirements evidence: Declared by Smithery, last synced Oct 28, 2026. Not independently verified by MCP Toplist.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Oct 28, 2026

Registry sightings

Smithery ↗listed since Oct 28, 2026 · still listed

Do you maintain IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow? to correct or enrich this profile.

VERSIONS

Version information unavailable

The registry that lists this server does not expose version metadata, and no release tags were found on the linked repository. MCP Toplist cannot say how, or whether, this server is versioned.

STANDING

#161,944of 162,202 active servers

Ranks ahead of 258 of 162,202 servers on MCP Toplist.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/smithery%2Ftofan96you%2Fincidentforge-mcp.svg)](https://mcptoplist.com/server/smithery%2Ftofan96you%2Fincidentforge-mcp)

HTML

<a href="https://mcptoplist.com/server/smithery%2Ftofan96you%2Fincidentforge-mcp"><img src="https://mcptoplist.com/badge/smithery%2Ftofan96you%2Fincidentforge-mcp.svg" alt="MCP Toplist: #161,944 of 162,202" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Is IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow listed on the Official MCP Registry?: IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow is not on the Official MCP Registry. It is listed on Smithery.
How many versions does IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow have?: Version information is unavailable for IncidentForge — Security Incident Response, Timeline, Severity, Communications & Blameless Postmortem Workflow: no registry that lists it exposes version metadata, and no release tags were found on its repository.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers