Skip to content

LogsLoom MCP server

io.github.efim23/logsloomefim23streamable-httpv0.1.1Scanned

Ingest and search LogsLoom logs from coding agents.

4 tools: 1 do something that can't be undone and 3 only read.

Tools: 0 delete, 1 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LogsLoom MCP server can do

The LogsLoom MCP server is published by the GitHub account efim23. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (logs_ingest), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (logs_ingest).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 1Claude Code: ask
  • logs_ingestSend one or many log events to LogsLoom (POST /v1/logs).Reads text others writeNo findings

    Why it is in this group

    • The name "logs_ingest" says "log": a word for reading.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe description's first sentence says "send" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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).
Only reads 3Show 3 read-only tools
  • logs_getFetch one log by id.No findings

    Why it is in this group

    • The name "logs_get" says "log": a word for reading.
    Description, as the server wrote it
    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_listThere is no user-session projects API.No findings

    Why it is in this group

    • The name "logs_projects_list" says "log": a word for reading.
    Description, as the server wrote it
    There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.logsloom.com/mcp: tools/list returned 4 tools to an anonymous client, including logs_ingest (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http logsloom https://mcp.logsloom.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http logsloom https://mcp.logsloom.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__logsloom__logs_search",
      "mcp__logsloom__logs_get",
      "mcp__logsloom__logs_projects_list"
    ],
    "ask": [
      "mcp__logsloom__logs_ingest"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as logsloom. Review it before you use it.

Capability tags behind 1 rule
  • mcp__logsloom__logs_ingest untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.efim23/logsloom/verify?hash=65091db52db55d8b413b8fe06cbf82d84f510290b48af0285d9e461745f4623c" | jq -e '.changed == false'

Pinned hash 65091db52db5, from Nov 19, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.efim23/logsloom/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.efim23/logsloom
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.efim23/logsloom.svg)](https://radar.anlyon.com/servers/io.github.efim23/logsloom)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.

LogsLoom MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LogsLoom MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LogsLoom MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LogsLoom MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: logs_ingest.

What tools does the LogsLoom MCP server have?

4 tools: 1 irreversible, 3 read. logs_ingest, logs_search, logs_get and logs_projects_list.

Does the LogsLoom MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LogsLoom MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the LogsLoom MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.