Caveat verdict

glm-mcp-server-use

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Configures and validates official GLM/Z.AI MCP servers using an API key from environment variables; all traffic goes to the documented api.z.ai endpoints for legitimate AI service calls.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

58
security
80
transparency
70
maintenance

Findings (3)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="your_zai_api_key

Pattern match medium

subprocess execution — runs system commands from Python

scripts/setup_glm_mcp_servers.py · prose · downgraded · subprocess.run(

Pattern match low

Python os.getenv — reads environment variable

scripts/get_zai_api_key.py · prose · downgraded · os.getenv(

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

network_in

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API