mcp-server-kling@0.6.0
VERIFIED· not startedPublisher claims: "Kling AI video generation MCP server for Model Context Protocol hosts" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
KLING_ACCESS_KEYKLING_SECRET_KEYConfiguration, not credentials: MCP_HOST_BRIDGE_STATE, MCP_WORKSPACE_PATH, MINDSTONE_REBEL_BRIDGE_STATE, TASK_TYPE_PATHS- Where it talks to
- no vendor host named in the codeAlso klingai.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names klingai.com as well as its own vendor. The guard injects KLING_ACCESS_KEY, KLING_SECRET_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.5.0
vet-skills diff mcp-server-kling 0.5.0 0.6.0In the sandbox, this version reached for nothing 0.5.0 did not. Compared from the two recorded runs, not from source.
0.5.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-22 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 7 s · 2 scenarios · 0 deviationsStatic findings
* * A static deny-list of sensitive paths (`~/.ssh/**`, `~/.aws/**`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."build": "tsc && shx chmod +x dist/index.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.* arbitrary files (`~/.zshrc`, `~/.ssh/authorized_keys`, `/etc/cron.daily/x`),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return { hit: true, reason: '~/.ssh/** is sensitive' };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* * A static deny-list of sensitive paths (`~/.ssh/**`, `~/.aws/**`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return { hit: true, reason: '~/.aws/** is sensitive' };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* arbitrary files (`~/.zshrc`, `~/.ssh/authorized_keys`, `/etc/cron.daily/x`),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.'Sensitive paths (~/.ssh, ~/.aws, /etc, ~/.bashrc, ~/.zshrc) are refused even when the root would otherwise permit them. ' +Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.