Skills/npm/ai-cx-mcp

ai-cx-mcp@0.3.0

CAUTION· startup only

Publisher claims: "MCP server for the Flyle AI CX public API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher flyle · publishing for 51 daysInstalls 27,521Last detonated 3d ago

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Caution 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
no credential variables read in the code
Where it talks to
flyle.io (its own)
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable and talks to flyle.io, its own; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @flyle/ai-cx-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 22 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
2.1sprocessdependency install exit 0
22sfilesystemread ~/work/.flyle-ai-cx-mcp/workspace.json outside project
22sclaimedstartup only: exited (0) before answering · (node:622) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) この作業ディレクトリはまだログインしていません。このディレクトリで `npx @flyle/ai-cx-mcp@latest login --tenant <テナント名>` を実行してから、MCP サーバーを起動し直してください。
22sprocessscript backend runs setup only
22sprocessno install scripts to re-run

Static findings

No findings across 272 lines in 5 files.

Cost to the agent

Instructions loaded
≈46 tok
1 file · 5 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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

No advisories in OSV for @flyle/ai-cx-mcp@0.3.0 as of 3d ago. This is the package itself, not its dependencies.

What would make this Verified

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim flyle: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim flylePropose a patch to the maintainer