jzt-sepp-mcp-server (zhengziha/jzt-sepp-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 11 tools. No publisher has claimed this listing.

Emerging

74/100

jzt-sepp-mcp-server

Item: jzt-sepp-mcp-server
Rating: 74
Author: M8ven

→ zhengziha/jzt-sepp-mcp-server · listed on github_repo_search

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 push why connect →

Who stands behind it

zhengziha

Source: github_repo_search

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

GitHub

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 3 credentials: SEPP_PASSWORD, SEPP_AUTH_TOKEN, SEPP_SMTP_PASSWORD

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.

configSEPP_CONFIG

configSEPP_USERNAME登录报 "未配置账号密码"： / SEPP_PASSWORD 为空，且没有有效 cookie / token。

🔐 secretSEPP_PASSWORD登录报 "未配置账号密码"：SEPP_USERNAME / 为空，且没有有效 cookie / token。

🔐 secretSEPP_AUTH_TOKEN2. （浏览器里复制的 sepp-auth JWT）；

configSEPP_USER_ID

configSEPP_USER_NAME

configSEPP_USER_ACCOUNT

configSEPP_PRODUCT_ID

configSEPP_MONITOR_USERS新增监控。responsers=["郑益2","房航"] 一次监控多人；不填时用 SEPP_MONITOR_USERS 配置，否则默认"我"；支持轮询间隔 + 新增/超时提醒开关

configSEPP_HEADLESSnormal_auth 失败 / 想手动过验证码：=false 首次登录手动过验证；或直接配置 SEPP_AUTH_TOKEN。

configSEPP_ALLOW_SSO_LOGIN~~Playwright Keycloak SSO 明文表单~~ 默认禁用（明文密码会被计入错误次数、连续 5 次锁定账号），仅当显式设置 =true 才作为最后兜底。

configSEPP_LOGIN_TIMEOUT

configSEPP_COOKIE_FILE

configSEPP_PROFILE_DIR

configSEPP_STATE_FILE

configSEPP_DEFAULT_STATUS

configSEPP_ACTIVE_STATUSES

configSEPP_TIMEOUT_HOURS

configSEPP_WEBHOOK_URL

configSEPP_WEBHOOK_TYPE

configSEPP_DINGTALK_AT_MAP负责人 @：配置（姓名 → 钉钉手机号）后，命中映射的负责人用手机号 @（触发钉钉提醒）；未命中或未配置则负责人名称加粗显示。

configSEPP_SMTP_HOST

configSEPP_SMTP_PORT

configSEPP_SMTP_USER

🔐 secretSEPP_SMTP_PASSWORD

configSEPP_SMTP_SSL

configSEPP_EMAIL_TO

// 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

11/11 tools missing one or more hints — login_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_user_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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.).

Tests exist

No test files found

Add tests that exercise each declared tool.

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/zhengziha/jzt-sepp-mcp-server)](https://m8ven.ai/mcp/zhengziha/jzt-sepp-mcp-server)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: c77bcba44c49769698faa91160c58731377631b6

code hash: 12d45bac1d47952df4be1882b12e35130c7d034eb5abef58e184d8b8f07432db

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