Skills/PyPI/ads-onyx-mcp

ads-onyx-mcp@0.8.0

VERIFIED· install only

Publisher claims: "MCP server for Ads.Onyx — a client-side façade over the platform's REST API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher alchimiedatasolutions · publishing for 81 daysInstalls 335Last detonated 15 min ago
$claude mcp add ads-onyx-mcp -- uvx ads-onyx-mcp
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 38 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

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
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso monclient.fr, aspnetboilerplate.com, xmlsoap.org — 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
use of the skill by an agent

Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx ads-onyx-mcp

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

What changed since 0.7.0

vet-skills diff ads-onyx-mcp 0.7.0 0.8.0

In the sandbox, this version reached for nothing 0.7.0 did not. Compared from the two recorded runs, not from source.

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; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-22 and scored it 85/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 · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: ImportError: attempted relative import with no known parent package
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: ModuleNotFoundError: No module named 'pydantic'
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.3sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.3sprocessbundled script run in the sandbox with no arguments
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocessexited 1: ModuleNotFoundError: No module named 'fpdf'
0.4sprocessbundled script run in the sandbox with no arguments
0.6sprocessexited 1: ModuleNotFoundError: No module named 'mcp'
0.6sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.6sprocessexited 1: ModuleNotFoundError: No module named 'httpx'
0.6sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.7sprocessexited 1: ModuleNotFoundError: No module named 'httpx'
0.7sprocess8 of 38 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.7sprocessscript backend runs setup only
0.7sprocessscript backend runs setup only
0.7sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathspyproject.toml:106 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesinclude = ["src", "README.md", "CHANGELOG.md", "LICENSE", "pyproject.toml", ".env.example"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/__main__.py:70 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Charge un ``.env`` local, pour le confort du développement seulement.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/__main__.py:84 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filespath = os.environ.get("ONYX_ENV_FILE", ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/__main__.py:377 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesVoir .env.example et le README.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/config.py:7 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesCe module ne connaît rien du transport. Il ne lit jamais de fichier `.env` par lui-même :Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/__main__.py:106 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv_path = os.path.abspath(os.environ.get("ONYX_ENV_FILE", ".env")) if from_dotenv else NoneFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/tools/shell.py:125 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesun **ensemble de caractères**, pas un préfixe : ``../../etc/passwd.py`` devenait doncFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/tools/env_block.py:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files**Le format n'est pas celui d'un fichier ``.env``**, et la différence mord. Il est défini parFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
MCP server using network transport (SSE/HTTP)src/onyx_mcp/__main__.py:438 · MCP server using network transport (SSE/HTTP) — data sent over network# `MCPServer.run` gère lui-même la boucle asyncio et l'arrêt propre. Le client HTTP, lui,Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
HIGH
Access to sensitive file pathssrc/onyx_mcp/tools/env_block.py:203 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"variable. It is not a .env file and not a single block of text: Onyx parses this "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/config.py:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``.mcp.json``). Le fichier `.env` n'existe que pour le confort du développement local, etFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/tools/scripts.py:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files``.env`` et réserve cinq pièges, est traité dans ``env_block``.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/tools/env_block.py:31 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesguillemets compris. C'est la faute la plus facile à faire en venant d'un fichier ``.env``.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/config.py:191 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Un nom vide vaut absent : un `.env` avec `ONYX_TENANT=` ne doit pas passer pourFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/config.py:41 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Pas de `env_file` ici : le chargement d'un `.env` est une décision du pointFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/onyx_mcp/config.py:161 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Un identifiant vide vaut absent, pour qu'un `.env` gardant `ONYX_USER=` à côtéFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈55 tok
1 file · 49 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.