Incident Timeline
Summarize local log timeline gaps and severity counts without returning messages, IDs, paths, or...
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y incident-timeline-mcp
MCP client config
{
"mcpServers": {
"incident-timeline": {
"command": "npx",
"args": [
"-y",
"incident-timeline-mcp"
]
}
}
}incident-timeline-mcp
Incident Timeline turns local timestamped logs into a coarse operational summary: file and line counts, severity totals, timestamp coverage, and the largest observed time gap.
Quick start
npm install
npm test
npm start
Use summarize_incident_timeline with a bounded project or log directory.
Privacy and limits
Log messages, timestamps, IDs, paths, IP addresses, and filenames are suppressed. The parser recognizes a conservative timestamp shape and broad severity words. It is a triage aid, not a forensic report.
