rayonne-mcp@0.13.2
CAUTION· not startedPublisher claims: "Rayonne MCP server — pilote un ou tous les espaces d'une organisation Rayonne (audit marketing, analyse produit, contenus, vidéos, métriques AARRR) depuis tout agent compatible MCP." 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: 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
RAYONNE_API_KEYRAYONNE_CREDENTIALS_FILERAYONNE_PLUGIN_API_KEYUV_PUBLISH_TOKENConfiguration, not credentials: CLAUDE_CONFIG_DIR, CLAUDE_SECURESTORAGE_CONFIG_DIR, RAYONNE_API_URL, RAYONNE_READ_ONLY- Where it talks to
- no vendor host named in the codeAlso sponge-theory.dev — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- 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 sponge-theory.dev as well as its own vendor. The guard injects RAYONNE_API_KEY, RAYONNE_CREDENTIALS_FILE, RAYONNE_PLUGIN_API_KEY, UV_PUBLISH_TOKEN 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.
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-15 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. Notable findings: Prompting user to enter sensitive credentials; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
raise SetupError("Enter the API key without spaces or the Bearer prefix")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Keep, kill or extend an experiment whose end date passed — confirmingFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.monkeypatch.setattr("sys.stdin", io.StringIO("sk_live_not_rayonne"))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.brief's facts cite. Secrets files (.env, keys, credentials) are refusedFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- **Jamais de secret ni de donnée client.** Ne lis pas `.env`, les clés, lesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.decide_experiment (keep / kill / extend at the end date)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# 2. ~/.pypirc [pypi] password (the global PyPI token, chmod 600)Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.@pytest.mark.parametrize('url', ['http://example.com', 'https://user:[email protected]',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.then gives the keep / kill / extend recommendation. Ask the founder forFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.run(cmd, capture_output=True, text=True, check=False).stdoutFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run(["osascript", "-e", script], capture_output=True, text=True, check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.content_marketing, geo); past that, too little volume is a « kill »."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(command, input=json.dumps(request), capture_output=True,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`recommendation` keep / kill / extend waiting for the founder."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- **Jamais de secret ni de donnée client.** Ne lis pas `.env`, les clés, lesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(["/usr/bin/osascript", "-e", script, prompt, default], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r"^(\.env(\.[\w.-]+)?|\.npmrc|\.pypirc|\.netrc|id_(rsa|dsa|ecdsa|ed25519)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.dans un dépôt, un `.env` ou un fichier versionné. Ne demande JAMAIS laFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run([sys.executable, str(mcp / 'build/sync_codex_skills.py'), '--check'], check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.@pytest.mark.parametrize("name", [".env", ".env.production", "server.pem", "id_rsa", "credentials.json"])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.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Prompting user to enter sensitive credentials≈ +9 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Unclaimed publisher≈ +8 on the totalClaim sponge-theory-contact: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Stripe-like API key pattern detected≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.