MCP servers › io.github.hu-chenyu › log-ai-compressor

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.hu-chenyu/log-ai-compressor

Local log forensics: compress logs into citable evidence with root-cause confidence tiers. — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedversion 2.12.5PythonMITstandard input/output8 tools

Summary

io.github.hu-chenyu/log-ai-compressor is a local MCP server listed in the official MCP registry at version 2.12.5. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 8 tools, 0 resources and 0 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: PyPI · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 8
Described as changing data: 1 of 8 toolsAI-classified
Mainly works on: files and code on the machine it runs onAI-classified
Topic: developer-toolsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

1 tool is described as changing something (export_report): our AI model's reading of the descriptions, not something we tested. We did not call it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

2.12.5, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-18 (earliest version still in the registry; older removed versions would be earlier)

Version history

10 versions listed, 2026-10-18 to 2026-10-20; 10 in the 90 days before the 2026-10-23 snapshot.

Most recent 10 versions

2.12.5 · 2026-10-20
2.12.4 · 2026-10-20
2.12.3 · 2026-10-19
2.12.2 · 2026-10-19
2.12.1 · 2026-10-19
2.12.0 · 2026-10-19
2.11.5 · 2026-10-19
2.11.4 · 2026-10-18
2.11.3 · 2026-10-18
2.11.2 · 2026-10-18

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.12.5 (published 2026-10-20).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

8tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

1 of 8 tools are described as changing something (creating, editing, deleting, sending or running).

analyze_log_filereads or searches
“分析一个或多个本机日志文件（按 mtime 从旧到新合并，适用于轮转日志），返回：统计概览 + 按优先级排序的错误簇 + 根因判定 + 异常标记。输出已经过聚类去重，token 消耗比读原始日志低几个数量级。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
11 inputs, 1 required
- pathsarrayrequired
- levelsarray or null
- includearray or null
- excludearray or null
- context_linesinteger
- similaritystring
- analysis_modestring
- rulestring
- top_ninteger
- encodingstring
- max_linesinteger or null
analyze_log_textreads or searches
“直接分析一段日志文本（用户粘贴的内容、命令输出、Agent 读到的片段）。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs, 1 required
- textstringrequired
- sourcestring
- levelsarray or null
- context_linesinteger
- similaritystring
- analysis_modestring
- rulestring
- top_ninteger
compare_log_filesreads or searches
“对比 2~5 个日志文件，列出相对基准文件的「新增 / 消失 / 共同」错误，适配版本回归验证与修复前后对比。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
- pathsarrayrequired
- levelsarray or null
- includearray or null
- excludearray or null
- context_linesinteger
- rulestring
export_reporton 5 other serversdescribed as changing data
“把指定日志文件导出为压缩报告。Markdown 格式专为投喂 LLM 优化（概览 + Top N 清单 + 典型样例详情），通常比原始日志小 50~500 倍。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs, 1 required
- pathsarrayrequired
- formatstring
- levelsarray or null
- top_ninteger
- context_linesinteger
- similaritystring
- analysis_modestring
- rulestring
- redactboolean
get_cluster_detailreads or searches
“对某个日志文件取单个错误簇的完整证据：典型样例原始行、前后上下文、降噪堆栈（业务帧高亮、系统库帧已折叠）、变量取值分布、全部实例。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 2 required
- pathstringrequired
- cluster_idintegerrequired
- levelsarray or null
- context_linesinteger
- similaritystring
- analysis_modestring
- rulestring
verify_evidenceon 3 other serversreads or searches
“取证自校验：核对结论的出处是否仍与原始日志一致。传 report_path 复核一份已导出的 JSON 报告（推荐：报告发出后日志可能已被修改或轮转清理）；只传 path 是当场自检。返回 VERIFIED / TAMPERED / UNVERIFIABLE / NO_EVIDENCE。**UNVERIFIABLE 不等于 TAMPERED**：前者是「源读不到，验不了」，后者是「回读过了，对不…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- pathstring or null
- report_pathstring or null
- levelsarray or null
- context_linesinteger
- similaritystring
- analysis_modestring
- rulestring
list_ruleson 32 other serversreads or searches
“列出内置的日志解析规则模板及其适用场景。日志格式没被正确解析时先看这里。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
check_environmenton 4 other serversreads or searches
“确认工具是否可用、内置规则、AI 解读是否已配置。不传参数即可自检。”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 8 tools
Says what it returns: 100% of 8 tools
States limits, defaults or errors: 0% of 8 tools
Says when to use it: 100% of 8 tools
Items covered per tool: 3.0 of 4 on average

Counted from the listing

Parameters with a description: 0% of 48
Tools with a description: 100% of 8
Typical description length: 85 characters

The tool set

Counted from the listing

Tools: 8
Size of the list: about 1,964 tokens for an agent to load (characters ÷ 4)
Naming: 8 of 8 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 8 of 8 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 2.12.5
Latest stable: 2.12.5
Status: current
Withdrawn: no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-eb4597f36f0ecda33…
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 0 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 2.12.5 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/hu-chenyu/log-ai-compressor	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.hu-chenyu
GitHub owner: a personal account (hu-chenyu)

Repository: github.com/hu-chenyu/log-ai-compressor
Stars: 1
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 1 star (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.hu-chenyu/log-ai-compressor

Answered from the data above

Is io.github.hu-chenyu/log-ai-compressor safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.hu-chenyu/log-ai-compressor been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.hu-chenyu/log-ai-compressor do?

It lists 8 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.hu-chenyu/log-ai-compressor change or delete data?

1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.hu-chenyu/log-ai-compressor publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 2.12.5, the latest stable release on PyPI.

Where is the source code of io.github.hu-chenyu/log-ai-compressor?

In github.com/hu-chenyu/log-ai-compressor, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.thedaviddias/front-end-checklistFront-End Checklistalso has tools that reads or searchescompare with this one
io.github.DeusData/codebase-memory-mcpCodebase Memoryalso has tools that reads or searchescompare with this one
io.github.yamadashy/repomixRepomixalso has tools that reads or searchescompare with this one
io.github.compiler-explorer/compiler-explorerCompiler Exploreralso has tools that reads or searchescompare with this one
com.gitdiagram/gitdiagramGitDiagramalso has tools that reads or searchescompare with this one
io.github.tester-army/e2ee2ealso has tools that reads or searchescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
1,839 msConnected after 0 redirects.
Read the inventory: 8 tools, 0 resources, 0 prompts.
2,361 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

pypi

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

0 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.hu-chenyu/log-ai-compressor: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.hu-chenyu/log-ai-compressor

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.hu-chenyu/log-ai-compressor)](https://protocolprobe.com/mcp/servers/io.github.hu-chenyu/log-ai-compressor)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology