LogsLoom

Last 30 days

Uptime

100%

Response time

183 ms typical, 183 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "logsloom": {
      "type": "http",
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}

4 tools

• logs_ingest

  Send one or many log events to LogsLoom (POST /v1/logs). Provide a single event via level+message, or a batch in `events` (max 100).

• logs_search

  List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset.

• logs_get

  Fetch one log by id. The HTTP API has no GET /v1/logs/:id yet, so this tries that path and falls back to searching the latest list page.

• logs_projects_list

  There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs).

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks