LogSentinel MCP Server

by evozim Your server? Claim it

answering

LogSentinel is answering right now. Last checked 1 min ago.

Anthropic logs audit filter and cybersecurity threat analyzer.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

93 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add logsentinel --transport http https://logsentinel-mcp.vercel.app/api/mcp

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

{
  "mcpServers": {
    "logsentinel": {
      "url": "https://logsentinel-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.logsentinel]
url = "https://logsentinel-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "logsentinel": {
      "url": "https://logsentinel-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "logsentinel": {
      "url": "https://logsentinel-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://logsentinel-mcp.vercel.app/api/mcp	sse	needs auth	91 ms	1 min ago

Alternatives to LogSentinel

same job, measured the same way

Log

by rog0x

Log parse, filter, analyze for AI agents

29 installs/wk local only

Cybersim Pro

by kayembahamid

Cybersecurity training, simulation, and incident response MCP server

local only

Claude Code Usage

by wheelbarrel00

Claude Code token usage, cost, and plan limits from local logs and Anthropic's usage API.

28 installs/wk local only

AgenTrux

by agentrux

Authenticated event topics for agent-to-agent messaging with per-agent credentials and audit logs.

answering

Cordon for MCP

by marras0914

Cordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals.

44 installs/wk local only

ThornGuard

by qwady-thorns

Remote MCP security gateway for auth, redaction, policy enforcement, and audit logging.

local only

Clevername

by alexfloyd13

AI agent governance — security scanning, BYOK routing, audit logging, and Council approvals.

58 installs/wk local only

SendGrid Secure

by choppaaahh

Security-first SendGrid MCP server: dry-run default, recipient allowlists, rate caps, audit log.

159 installs/wk local only

LogSentinel — questions

Answers built from our own checks of this server.

Why is there no tool list for LogSentinel?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is LogSentinel working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 93 ms. The bar chart above shows every period we have measured.

How do I connect LogSentinel?

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 is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does LogSentinel need an API key?

Yes. Every time we knock, LogSentinel answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is LogSentinel?

It answers our handshake in 93 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.