Logmcp runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 25 Aug 2026.
MCP server — read-only log access for AI assistants, without giving AI shell access.
We read the source, 20 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
return fmt.Errorf("chown root:logmcp %s: %w", dir, err)
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
path := filepath.Join(dir, name)
telegramAPIBase = "https://api.telegram.org/bot"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Logmcp and you get told the day something new turns up.
MCP server providing Prometheus metrics access and PromQL query execution for AI assistants
MCP server for Box admin-log analytics — external-sharing visibility, read-only
SigNoz MCP server: access metrics, traces, logs, alerts, and dashboards via AI assistants
Read-only admin MCP server for LastSaaS — dashboards, users, tenants, billing, logs, health.
MCP server for Sentry — error tracking, issues, releases, events, and projects for AI assistants.
MCP server for Yandex.Metrica Stat API (read-only).
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
MCP server for Microsoft Entra ID sign-in and audit-log triage (read-only)
Answers built from our own checks of this server.