Skills/PyPI/oxyo-mcp

oxyo-mcp@1.2.4

VERIFIED· not started

Publisher claims: "Continuously cut Claude Code, Codex, Cursor & VS Code token and quota burn by 60-72% via persistent contradiction-free memory, root-cause tracking & deterministic verification (oxyo.si)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher eno654 · publishing for 3 daysInstalls 407Last detonated 5 h ago
$claude mcp add oxyo-mcp -- uvx oxyo-mcp
WatchReport an issue

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
OXYO_API_KEYConfiguration, not credentials: OXYO_MCP_URL
Where it talks to
oxyo.si (its own)
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. It asks for OXYO_API_KEY and talks to oxyo.si. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets OXYO_API_KEY=oxyo.si -- uvx oxyo-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; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 80/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 · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

CRITICAL
README directs the reader to a committed installerREADME.md:20<a href="https://oxyo.si/download/Oxyo-Setup.exe"><img src="https://img.shields.io/badge/Windows_App-.exe_Installer-3b82f6?style=for-the-badge&logo=windows&logoColor=white" alt="Windows App"></a>Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
README links to an external installerREADME.md → https://oxyo.si/download/Oxyo-Setup.exehttps://oxyo.si/download/Oxyo-Setup.exeFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈81 tok
1 file · 13 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 oxyo-mcp@1.2.4 as of 4 h ago. This is the package itself, not its dependencies.