Ext Ops Panel
Open dashboard
Comparison

log-sleuth vs LogsLoom

log-sleuth is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

log-sleuth is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. LogsLoom is an MCP server published by efim23. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacelog-sleuthLogsLoom
Community marketplace barnburner121/claude-plugin-marketplace Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (npm): 82
Downloads/week (npm): 16
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

log-sleuth vs LogsLoom
Factlog-sleuthno longer listed · LogsLoom
Marketplaces that list it (differs)01
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@barnburner121/plugin-hub-mcp)Remote server (mcp.logsloom.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/barnburner121/claude-plugin-marketplacegithub.com/efim23/logsloom
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of log-sleuth

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • gonzo

    Set up and use Gonzo, the open-source terminal log analysis tool. Detects deployment platforms (Vercel, Supabase, K8s, Docker, AWS, Cloudflare, Fly, Render, Railway, Netlify…

    by ControlTheory · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ctrlb-decompose

    Analyze log files with ctrlb-decompose — pattern clustering, anomaly detection, and severity scoring

    by CtrlB · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Log Detective MCP

    MCP server providing log snippet and Python traceback extraction tools.

    by fedora-copr · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Jarroba Tools · Logs

    Lets your AI read a CI log far too big for its context. 12 tools, takes a file path.

    by Invarato · MCP server

    Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job

  • log-analyzer-mcp io.github.Fato07/log-analyzer-mcp

    AI-powered log analysis - parse, search, extract errors across 9+ formats

    by Fato07 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • sumo-logic

    Query Sumo Logic logs, alerts, dashboards, and SIEM insights directly from Copilot.

    by SumoLogic · Plugin bundle

    Listed on: Copilot CLI: github/awesome-copilot · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

log-sleuth

In its own words, on Community GitHub marketplaces:

Analyze log files for patterns, search with structured queries, get logging recommendations, and correlate across services

LogsLoom

In its own words, on Official MCP Registry:

Ingest and search LogsLoom logs from coding agents.

How to run each

log-sleuth

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

LogsLoom As a remote MCP server

Claude Code
claude mcp add --transport http logsloom https://mcp.logsloom.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: LOGSLOOM_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only LogsLoom has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of log-sleuth publish no settings it asks for, so we do not compare settings.

What it can do: log-sleuth · What it can do: LogsLoom · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built