mcpbeat Sign in

Incident Timeline MCP Server

local only

Incident Timeline MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 9 Aug 2026.

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

Installs / week
npm · incident-timeline-mcp
0
Stars
0 open issues
9 Aug 2026
Last commit
0 releases in 90 days
License
TypeScript

Nothing serious here today

Today is the operative word: we check Incident Timeline MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

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.

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": {
      "args": [
        "-y",
        "incident-timeline-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.incident-timeline-mcp]
command = "npx"
args = ["-y", "incident-timeline-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "incident-timeline-mcp": {
      "args": [
        "-y",
        "incident-timeline-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "incident-timeline-mcp": {
      "args": [
        "-y",
        "incident-timeline-mcp"
      ],
      "command": "npx"
    }
  }
}

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.

29 installs/wk local only
Logmcp
by kascada

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

local only
Hyperping
by hyperping

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

26 tools answering
Appsignal
by pulsemcp

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

104 installs/wk local only
Reps
by repsworkout

Your Reps gym log in Claude or ChatGPT: workouts, PRs, progress, routines and training plans.

answering
Devloop
by vincentvella

Browser + dev-server logs on one correlated timeline, for Claude Code and AI agents.

42 installs/wk local only
OntoRamp Decision Intelligence
by ontoramp

Log, evaluate, and ground AI decisions against authority context. Returns PASS, WARN, or BLOCK.

answering
Marchward
by marchward

Runtime authority for AI agents: credential mediation, spend cap, approval gates, audit log.

36 installs/wk local only

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.
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 with the file path 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.
Is Incident Timeline MCP open source?
We cannot say either way: written in TypeScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.