CLS MCP Server (Tinker-LGD2026/cls-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 36 tools. No publisher has claimed this listing.

C
Emerging
74/100

CLS MCP Server

Provides a suite of 33 tools for interacting with Tencent Cloud Log Service (CLS), enabling log analysis, PromQL metrics queries, and resource management. It allows AI assistants to perform CQL/SQL retrieval, manage alarm strategies, and handle data processing tasks with tiered permission controls.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Tinker-LGD2026

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: CLS_SECRET_KEY, MCP_AUTH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCLS_HOST否 0.0.0.0 HTTP 监听地址(远程模式)
configCLS_SSE_HOST
configCLS_PORT否 8000 HTTP 监听端口(远程模式)
configCLS_SSE_PORT
configCLS_ENABLED_TOOLS否 — 工具白名单(逗号分隔),未设置则注册全部工具,详见下方说明
configCLS_SECRET_ID"": "替换为你的SecretId",
🔐 secretCLS_SECRET_KEY"": "替换为你的SecretKey",
configCLS_REGION"": "ap-guangzhou"
configCLS_TRANSPORT否 stdio 传输方式:stdio / sse / streamable-http
configCLS_STATELESS_HTTP
configCLS_ENABLE_WRITE权限说明:只读工具默认启用;⚠️ 写入工具需设置 =true;🚨 危险工具需同时设置 CLS_ENABLE_WRITE=true 和 CLS_ENABLE_DANGEROUS=true。
configCLS_ENABLE_DANGEROUS权限说明:只读工具默认启用;⚠️ 写入工具需设置 CLS_ENABLE_WRITE=true;🚨 危险工具需同时设置 CLS_ENABLE_WRITE=true 和 =true。
🔐 secretMCP_AUTH_TOKEN否 — HTTP Bearer Token 认证(远程模式,建议开启)
configCLS_LOG_LEVEL否 INFO 日志级别:DEBUG / INFO / WARNING / ERROR
configCLS_REQUEST_TIMEOUT否 60 SDK 请求超时时间(秒)
configCLS_RETRY_MAX_ATTEMPTS否 3 失败重试最大尝试次数(含首次调用)
configCLS_RETRY_BASE_DELAY否 1.0 重试基础退避延迟(秒),实际延迟会指数递增
configCLS_CB_FAILURE_THRESHOLD否 5 熔断器触发阈值:连续失败多少次后熔断
configCLS_CB_RECOVERY_TIMEOUT否 30 熔断恢复超时(秒):熔断后多久尝试恢复
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

36/36 tools missing one or more hints — cls_describe_alarms (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cls_describe_alarm_detail (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cls_describe_alarm_notices (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +33 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 7/36 tools referenced in tests (19%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/tinker-lgd2026/cls-mcp-server)](https://m8ven.ai/mcp/tinker-lgd2026/cls-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: acb09349a88c2327c2268d5b976ea5e344bae8d7
code hash: f8fb28b0033a915d3e923db8c9a9359ba29a2b9a3ecd62f3983c748b5c0b71cd
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client