Is Log10x safe and trustworthy?

tashan scores Log10x on public evidence — tashan score 74.0/100, it is currently active, no known advisories against the current release, its declared dependencies reach: credentials. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Log10x?

In Claude Code: run `claude mcp add log10x -- npx -y log10x-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Log10x

npm

Tools to rank log patterns by volume and cost and to compact, tier down or offload each pattern

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Data & Analytics — see all ranked ›

Install (Claude Code):

claude mcp add log10x -- npx -y log10x-mcp

thin

“says what it does, not how to use it — 0 tool docs, 1 worked examples”

This grade is wrong ›

tashan score: 74.0
Instruction depth: 46.0 (thin — shallow — says what it does, not how to actually use it)
Adoption: 6.1k/wk
Upkeep: 84.0
Freshness: 93.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 1.30.7 — this package, not its dependency tree

Handles credentials or secretsfrom declared dependencies

Signed build provenancepublished from public CI with an attestation

What changed recently

2026-08-17 log10x-mcp published 1.29.16, was 1.28.1 A new release is available.
2026-08-19 log10x-mcp published 1.29.22, was 1.29.16 A new release is available.
2026-08-27 log10x-mcp published 1.30.0, was 1.29.22 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 4 changes to Log10x in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-log10x-mcp.svg)](https://tashan.sh/capability/pkg-log10x-mcp.html)

npm ↗ · source ↗ · pkg:log10x-mcp

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?