structured-log vs io.github.Fato07/log-analyzer-mcp
structured-log is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
structured-log is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.Fato07/log-analyzer-mcp is an MCP server published by Fato07. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  io.github.Fato07/log-analyzer-mcp | |
|---|---|---|
| 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.4.2 Downloads/month (PyPI): 158 Downloads/week (PyPI): 34 Forks (GitHub): 1 Stars (GitHub): 5 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
| Fact | structured-logno longer listed · | io.github.Fato07/log-analyzer-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 5 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (codesdevs-log-analyzer) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/fato07/log-analyzer-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
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 structured-log
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Pydantic Logfire observability platform integration. Query traces, monitor application performance, analyze logs, and debug issues directly from Claude Code.
-
Add Logfire observability to Python applications with auto-instrumentation for FastAPI, httpx, asyncpg, SQLAlchemy, and more
-
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…
-
Deterministic dev tools for AI agents over MCP: hashing, encoding, formatting, codegen, and more.
-
Skills for building with Broadcast, a Swift logging package for structured logs, buffered destinations, and multi-session log export.
-
Ingest and search LogsLoom logs from coding agents.
What each says it does
structured-log
Generate structured logging for any language
io.github.Fato07/log-analyzer-mcp
AI-powered log analysis - parse, search, extract errors across 9+ formats
How to run each
structured-log
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.Fato07/log-analyzer-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio log-analyzer-mcp -- uvx codesdevs-log-analyzerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: structured-log · What it can do: io.github.Fato07/log-analyzer-mcp · 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.