# LogsLoom (remote · mcp.logsloom.com)

Ingest and search LogsLoom logs from coding agents.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.logsloom.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/efim23-logsloom/mcp.md), [page](https://verifymcp.io/servers/efim23-logsloom/mcp)
- npm · `@logsloom/mcp`: 31/100, [markdown](https://verifymcp.io/servers/efim23-logsloom/logsloom-mcp.md), [page](https://verifymcp.io/servers/efim23-logsloom/logsloom-mcp)

## Channel facts

- Endpoint: `https://mcp.logsloom.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 314 tokens (~78/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logs_ingest" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the LogsLoom MCP server?

LogsLoom is a hosted endpoint at https://mcp.logsloom.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http efim23-logsloom 'https://mcp.logsloom.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "efim23-logsloom": {
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "efim23-logsloom": {
      "type": "http",
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.efim23-logsloom]
url = "https://mcp.logsloom.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "efim23-logsloom": {
      "type": "remote",
      "url": "https://mcp.logsloom.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add efim23-logsloom --url 'https://mcp.logsloom.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  efim23-logsloom:
    url: "https://mcp.logsloom.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "efim23-logsloom": {
      "Transport": "http",
      "Url": "https://mcp.logsloom.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add efim23-logsloom -t streamable-http -u 'https://mcp.logsloom.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "efim23-logsloom": {
      "type": "http",
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 61)

First indexed and scored.

## MCP tools (4)

### `logs_ingest` (~121 tokens)

Ingest logs

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).

Input parameters:

- `environment` (string)
- `events` (array): Batch of events; overrides single-event fields when set
- `level` (string): Required unless `events` is set
- `message` (string): Required unless `events` is set
- `metadata` (object)
- `service` (string)
- `timestamp` (string)

### `logs_search` (~96 tokens)

Search logs

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

Input parameters:

- `level` (string)
- `limit` (integer): 1–100, default 50
- `offset` (integer): Pagination offset, default 0
- `q` (string): Case-insensitive message contains
- `service` (string): Exact service name

### `logs_get` (~58 tokens)

Get a log by id

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.

Input parameters:

- `id` (string, required): Log event id from ingest or search

### `logs_projects_list` (~39 tokens)

Current project scope

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/efim23-logsloom/mcp#diagnostics

## Score history

- 2026-09-20: 63
- 2026-09-19: 62
- 2026-09-18: 62
- 2026-09-17: 61

## Common questions

### What is the LogsLoom MCP server?

LogsLoom is an MCP server listed in the public MCP registry as io.github.efim23/logsloom. Ingest and search LogsLoom logs from coding agents. This page covers its hosted endpoint (https://mcp.logsloom.com/mcp).

### Is the LogsLoom MCP server safe to use?

LogsLoom scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LogsLoom MCP server expose?

LogsLoom exposes 4 tools: logs_ingest, logs_search, logs_get, logs_projects_list. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.

### Does the LogsLoom MCP server require authentication?

No. We connected to LogsLoom without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LogsLoom MCP server still maintained?

LogsLoom is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.logsloom.com/mcp
- Authorisation metadata: https://mcp.logsloom.com/.well-known/oauth-protected-resource/mcp
- Website: https://logsloom.com/
- Changelog RSS feed: https://verifymcp.io/servers/efim23-logsloom/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/efim23-logsloom/mcp.json
- HTML version of this page: https://verifymcp.io/servers/efim23-logsloom/mcp