log10x-mcpBLOCK
Log10x MCP Server — per-pattern log cost attribution for AI assistants (Claude, Cursor, Claude Desktop)
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Ask your AI assistant about log costs, log patterns, and incidents in plain English, and get structured answers backed by real per-pattern metrics. "Why did our log costs spike this week?", "what's driving payments-svc volume?", "pull the payment_retry events for acme-corp from Jan 15 to Apr 15." The server exposes the 10x platform to Claude and any MCP-compatible assistant as a set of tools.
10x groups your logs by message type. The same lines repeat over and over with only the timestamp or request ID changing, so 10x collapses each flood of near-identical lines into one message type and ranks them by volume and cost. That is how the answers stay exact instead of best-effort clustering, no regex required.
This server is open source under MIT. A Log10x product license (API key) unlocks the account-scoped tools; without one, the server boots read-only against a public demo dataset so the tools can be explored immediately.
What you can ask
b760aa90680fOBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add log10x-mcp --env LOG10X_API_KEY=${LOG10X_API_KEY} -- npx -y [email protected]Exposed tools (5)
4 read · 0 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
Attribution | read | Top patterns and savings are queryable; dependency_check can reach the SIEM. |
Commitment | read | Weekly commitment report + maintenance loop on overflow contents. |
Mitigation | destructive | Receiver in-path so compact / sample / drop actually take effect on the forwarder. |
Overflow | read | Overflow bucket (your own S3) sits between the forwarder and the SIEM — engine-marked noisy patterns route here instead of paying SIEM ingest. Events stay recoverable via fetch-back on demand (incident / audit). |
Visibility | read | Reporter installed — every pattern fingerprinted with cost attribution metrics flowing. |
Trust audit
BLOCKgrade F · trust 55/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (15 observation(s))
- Network
- declared (11 observation(s))
- Shell
- declared (5 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (25)
const { stdout } = await exec(const { stdout } = await exec(const { stdout } = await exec(const { stdout } = await exec(const { stdout } = await exec('kubeconfig, so nothing already in `~/.kube/config` is touched.',
missing: 'AWS_ACCESS_KEY_ID, AWS_PROFILE, or ~/.aws/credentials (instance roles are not auto-detected here)',
? [``, `> **Note:** Cross-account role \`${detectedRole}\` detected from \`~/.kube/config\` exec block and injected into the \`eks_exec_args\` local.`]'# Uses standard AWS credentials (env vars, ~/.aws/credentials, or IAM role)\npip3 install boto3',
const agent = new https.Agent({ rejectUnauthorized: false });dispatcher: new (await import('undici')).Agent({ connect: { rejectUnauthorized: false } }),'# Add --insecure here if your search head serves a self-signed certificate',
const req = https.request(new URL(url), { method: init.method ?? 'GET', headers, rejectUnauthorized: false }, (res) => {configure_env: { live: true, args: { nickname: 'doc-capture-dry-run', metricsBackend: { kind: 'log10x', apiKey: '4d985100-ee4a-4b6c-b784-a416b8684868', envId: '6aa99191-f827-4579-a96a-c0ebdfe73884' },apiKey: '4d985100-ee4a-4b6c-b784-a416b8684868',
apiKey: 'FAKE_TEST_FIXTURE_aaa111bbb222ccc333dd-this-looks-like-a-real-key',
auth: { type: 'bearer', token: 'sk-proj-2XpVxxTNAIMhqx1GquX0v71geiNqlMWfhDS4A4v9' },Mitigation
resolve(here, '../../product-kb/docs'),
resolve(here, '../../../product-kb/docs'), // belt-and-suspenders
resolve(here, '../../product-kb-data'), // legacy build-time copy name
resolve(here, '../../../product-kb-data'), // build/lib/ -> build/
resolve(here, '../../../../config/mksite/docs'), // repo sibling
url: `http://127.0.0.1:${addr.port}`,const url = `http://127.0.0.1:${addr.port}`;Gates applied: no_behavioural_pass.
b760aa90680ffull audit observations/trust-audit/mcp-server/log-10x__log10x-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | b760aa90680f | BLOCK | F | 55 | first audit |
Questions
What is the log10x-mcp MCP server?
Log10x MCP Server — per-pattern log cost attribution for AI assistants (Claude, Cursor, Claude Desktop)
What tools does log10x-mcp expose?
5 in total: 4 read-only, 0 that write, and 1 that can delete or overwrite (Mitigation). Every one is listed on this page with its risk.
Is log10x-mcp safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (55/100) and found 13 critical or high issues in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does log10x-mcp need?
It reads ARTIFACTORY_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AZURE_CLIENT_SECRET, AZURE_STORAGE_KEY, AZURE_WORKSPACE_KEY, CLICKHOUSE_API_KEY, CLICKHOUSE_PASSWORD, CX_SECRET, DATADOG_API_KEY and DATADOG_APP_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does log10x-mcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as log10x-mcp at 1.30.49.
How current is this page?
The grade is for one exact copy of the source (b760aa90680f), read on 2026-10-12. The repository is watched and re-audited when it changes.