Ext Ops Panel
Open dashboard
Comparison

loki vs Trade & Logistics Evidence

loki is a plugin bundle for AI coding tools published by lexfrei. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Trade & Logistics Evidence is an MCP server published by api.timzinin.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacelokiTrade & Logistics Evidence
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 3
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

loki vs Trade & Logistics Evidence
FactlokiTrade & Logistics Evidence
Marketplaces that list it11
Stars (GitHub) (differs)5No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/lexfrei/mcp-loki)Remote server (api.timzinin.com/mcp/trade-logistics)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)1Not a bundle
Licence (differs)BSD-3-ClauseNot stated
Repository (differs)github.com/lexfrei/mcp-lokiNot stated
Changes in the last 7 days00
First seen2026-10-112026-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. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

loki

In its own words, on Claude Code: claude-plugins-community:

MCP server for querying Grafana Loki logs. Enables LLMs to execute LogQL queries, discover labels and their values, explore log series by selectors, and retrieve index statistics — all via the Model Context Protocol. Supports basic auth, bearer token, and multi-tenant (X-Scope-OrgID) authentication.

Trade & Logistics Evidence

In its own words, on Official MCP Registry:

Pay-per-call shipping evidence: canal queues, tanker flows, container and carbon exceptions.

How to run each

loki As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install loki@claude-community

Trade & Logistics Evidence As a remote MCP server

Claude Code
claude mcp add --transport http trade-logistics https://api.timzinin.com/mcp/trade-logistics

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

Only Trade & Logistics Evidence 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 Trade & Logistics Evidence publish no settings it asks for, so we do not compare settings.

What it can do: loki · What it can do: Trade & Logistics Evidence · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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