Incident Timeline Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026

Summarize local log timeline gaps and severity counts without returning messages, IDs, paths, or...

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

A local MCP server that summarizes timestamped log files into coarse incident timelines: file and line counts, severity totals, time coverage and the largest…

What you can do
  • Summarize a bounded project or log directory into an incident timeline overview
  • Report file and line counts, severity totals, timestamp coverage and the largest observed time gap
  • Keep log messages, timestamps, IDs, paths, IP addresses and filenames out of the returned summary
When to use it
Useful for quick triage when you want an assistant to gauge the shape of local logs — how much was logged, how severe it looks, and where the biggest time gaps are — without exposing log contents. It is a triage aid rather than a forensic report.
Requirements
Runs as a local process over stdio, installed from the npm package incident-timeline-mcp; Node.js and npm are needed to install and start it. No authentication, environment variables or headers are declared. It reads local log directories on the machine.
Before you install
It reads local log files, so point it at a bounded directory rather than a broad filesystem path. The summary is deliberately coarse and the parser recognizes only a conservative timestamp shape and broad severity words, so treat results as triage, not a forensic or audit record.

Installation

In SourceWeft

  1. Open Incident Timeline Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

bash
npm installnpm testnpm 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.

Source: README.md at commit bdd5ab3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.