Lingxi (adrian803/lingxi) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
10 days ago

Lingxi

Autonomous penetration testing framework with MCP tool bridges for Kali Linux container management and CTF workflows.

→ adrian803/lingxi· listed on pulsemcp

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

adrian803

Source: PulseMCP

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 →

⚡ Connect GitHub for Live Monitored

Install from

PulseMCP

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: AGENT_BEARER_TOKEN, AGENT_TOKEN, COMPETITION_API_TOKEN, DEEPSEEK_API_KEY
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.
configLING_XI_IDLE_FETCH_SECONDS
configLING_XI_BUSY_FETCH_SECONDS忙碌拉题间隔 30
configLINGXI_TASK_SHUTDOWN_TIMEOUT
configFORUM_HISTORY_BOOTSTRAP_DELAY_SECONDS
configFORUM_HISTORY_BOOTSTRAP_REFRESH_SECONDS
configOPENAI_BASE_URL
configANTHROPIC_BASE_URL
configADVISOR_ANTHROPIC_BASE_URL
configDEEPSEEK_BASE_URL
configSILICONFLOW_BASE_URL
configKALI_MCP_MAX_WORKERS
configSLIVER_MCP_MAX_WORKERS
configSLIVER_ENABLEDSliver 扩展 false
configSLIVER_CLIENT_PATH/ _CONFIG / _ROOT_DIR Sliver 路径配置 见 .env.example
configSLIVER_CLIENT_CONFIG
configSLIVER_AUTO_ENABLE_IF_PRESENT检测到 Sliver 时自动启用 false
configSLIVER_CLIENT_ROOT_DIR
configLINGXI_API_GATEWAY_STATE_DIR
configFORUM_FLAG_LOG_PATH
configFORUM_MCP_MAX_WORKERS
configSERVER_HOST/ SERVER_HOST_FALLBACK 论坛扩展入口 留空
configSERVER_HOST_FALLBACKSERVER_HOST / 论坛扩展入口 留空
🔐 secretAGENT_BEARER_TOKEN
configFORUM_HISTORY_CONVERSATION_PAGE_SIZE
configFORUM_HISTORY_MESSAGE_PAGE_SIZE
configFORUM_HISTORY_KEY_LIMIT_PER_TYPE
configFORUM_HISTORY_FLAG_COMBO_LIMIT
configFORUM_MESSAGE_STATE_EVENT_LIMIT
configFORUM_MESSAGE_STATE_PENDING_REF_LIMIT
configFORUM_MESSAGE_STATE_CONTEXT_LIMIT
configFORUM_MESSAGE_STATE_FLAG_ATTEMPTS_PER_SYNC
configFORUM_MESSAGE_STATE_FULL_REFRESH_SECONDS
configFORUM_MESSAGE_STATE_SYNC_INTERVAL_SECONDS
configLEVEL2_1PANEL_PSESSION
configPLATFORM_API_EXECUTOR_WORKERS
configLINGXI_FLAG_RESCUE_PATH
configLINGXI_FLAG_RECOVERY_DELAYS
configCOMPETITION_API_BASE_URL未配置 COMPETITION_BASE_URL / 时，程序进入待命模式
configCOMPETITION_BASE_URL未配置 / COMPETITION_API_BASE_URL 时，程序进入待命模式
configCOMPETITION_SERVER_HOST_FALLBACK平台备用主机 留空
🔐 secretAGENT_TOKENyour-agent-token
🔐 secretCOMPETITION_API_TOKEN
configCOMPETITION_SERVER_HOST平台主机地址 同 COMPETITION_API_BASE_URL
configSHELL_TOOL_EXECUTOR_WORKERS
configHEAVY_SCAN_TIMEOUT
configDDDD2_PATHDDDD2 工具路径 ./dddd2
configDOCKER_CONTAINER_NAMEKali 容器名 kali-pentest
configLING_XI_UNSAFE_RAW_LOGS输出原始日志（调试用） 0
configLINGXI_LOG_FILE
configLING_XI_PYTHON
configMAIN_BATTLE_DEMO_ALLOWLIST
configLINGXI_ADVISOR_TIMEOUT
configLINGXI_SDK_CONNECT_TIMEOUT
configLINGXI_SDK_QUERY_TIMEOUT
configLINGXI_SDK_FIRST_RESPONSE_TIMEOUT
configLINGXI_SDK_IDLE_RESPONSE_TIMEOUT
configLINGXI_SDK_CLOSE_TIMEOUT
configLINGXI_SDK_STARTUP_RETRY_ATTEMPTS
configLINGXI_SDK_MAX_CONCURRENCY
🔐 secretDEEPSEEK_API_KEY
configDEEPSEEK_MODEL
configKALI_MCP_SERVER_PORT
configCOMPETITION_GATEWAY_LLM_MAX_RETRIES
configCOMPETITION_GATEWAY_LLM_MAX_TOKENS
configCOMPETITION_GATEWAY_LLM_MAX_CONCURRENCY
configCOMPETITION_GATEWAY_LLM_MIN_INTERVAL
configLING_XI_EXTERNAL_KB_MODE
configLING_XI_EXTERNAL_KB_TRIGGER_FAILURES
configLING_XI_KNOWLEDGE_DIR
configLING_XI_KNOWLEDGE_TOP_K
configKNOWLEDGE_SERVICE_HOST知识服务监听地址 127.0.0.1
configTOU_SERVICE_HOST
configKNOWLEDGE_SERVICE_PORT知识服务端口 8791
configTOU_SERVICE_PORT
configLING_XI_KNOWLEDGE_WRITEBACK
configLING_XI_KNOWLEDGE_INCLUDE_FAILURES
// 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

49/49 tools missing one or more hints — execute_command (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_python (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); submit_flag (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +46 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.

Tool test coverage

Only 10/49 tools referenced in tests (20%)

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

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (runtime_env.py:75)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

2 secret values sent to console.log

Redact or omit secret values from log output.

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 5 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/adrian803-lingxi-zti9uo)](https://m8ven.ai/mcp/adrian803-lingxi-zti9uo)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6b81f3cfcd8dce32a8c471fb035420ab029a6e62
code hash: ebeafbe5c969da08917084d2027ca869363c6b2b2410c9dd96ef5999d3a60e4b
verified: 8/18/2026, 9:44:23 PM
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