Incident Timeline MCP Server

by mrfentmen Your server? Claim it

local only

Incident Timeline MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 55 installs a week from npm.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 182 · avg 16 · +20% w/w

a month agotoday

Installs / week

npm · incident-timeline-mcp

—

Stars

on GitHub

—

Last commit

3 releases in 90 days

—

License

language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add incident-timeline-mcp -- npx -y incident-timeline-mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "incident-timeline-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "incident-timeline-mcp"
      ]
    }
  }
}

~/.codex/config.toml

[mcp_servers.incident-timeline-mcp]
command = "npx"
args = ["-y", "incident-timeline-mcp"]

.cursor/mcp.json

{
  "mcpServers": {
    "incident-timeline-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "incident-timeline-mcp"
      ]
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "incident-timeline-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "incident-timeline-mcp"
      ]
    }
  }
}

Alternatives to Incident Timeline MCP

same job, measured the same way

Ndjson Local Log Triage MCP

by vola-trebla

Streams NDJSON log triage: query patterns, detect anomalies, summarize timelines without full load.

54 installs/wk local only

CLIO Parallel Sort

by iowarp

Sort, filter and summarize large log files by timestamp, level or keyword.

local only

InstaClock

by instaclock

Personal time tracker: start timers, log time and summarize your hours by activity.

answering

Logmcp

by kascada

MCP server — read-only log access for AI assistants, without giving AI shell access.

local only

Visualping

by webmonitoring

Visualping: monitor web pages for changes, review change timelines, and get alerts.

answering

Hyperping

by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

69 tools answering

Appsignal

by pulsemcp

MCP server for AppSignal — get alert details, search logs, and retrieve logs within time ranges.

129 installs/wk local only

Staygreen

by phuryn

Uptime monitoring and status pages for apps built with coding agents: status, incidents, setup.

164 installs/wk answering

Incident Timeline MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Incident Timeline MCP?

Incident Timeline MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package incident-timeline-mcp was installed 55 times last week.

Is Incident Timeline MCP still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Incident Timeline MCP?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls incident-timeline-mcp straight from npm; nothing to host, nothing to sign up for.

How many people use Incident Timeline MCP?

The npm package incident-timeline-mcp was installed 55 times in the last week. Week over week that is +20%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.