Append Log MCP runs on your own machine — the client starts it, so there is no endpoint to ping.
A generic append-only log MCP server. Persist timestamped JSON entries and query them by recency.
Nothing serious here today
Today is the operative word: we check Append Log MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Append Log MCP
same job, measured the same wayRead-only MCP server: query_metrics over local metric time-series (Quellgeist triage).
Read-only MCP server: query_logs over a structured JSONL incident log (Quellgeist triage).
Read-only MCP server: get_recent_commits over a local deploy log (Quellgeist triage).
Read-only Grafana Loki for AI agents: label discovery, bounded LogQL queries, counts, exports
Query a running k6: runtime status and metric list. Endpoints per k6 REST API docs.
Access New Relic observability data through MCP - query metrics, logs, traces, entities, and more
Read contacts, projects, documents and log entries, and run read-only queries in HERO Software.
MCP server for Microsoft Entra ID sign-in and audit-log triage (read-only by default)
Append Log MCP — questions
Answers built from our own checks of this server.