ads-onyx-mcp@0.8.0
VERIFIED· install onlyPublisher 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.
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.
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.0In 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 deviationsStatic findings
include = ["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."""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.path = 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.Voir .env.example et le README.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Ce 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.dotenv_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.un **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.**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.# `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."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.``.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.``.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.guillemets 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."""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.# 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."""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.Cost to the agent
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.