Skills/PyPI/mcpxyz

mcpxyz@0.4.0

VERIFIED· not started

Publisher claims: "MCP server for trade.xyz: analysis and trading of the xyz HIP-3 markets (xyz:AAPL, xyz:GOLD, ...) on Hyperliquid, with in-code guardrails." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher akugone · publishing for 105 daysInstalls 67Last detonated 3d ago
$claude mcp add mcpxyz -- uvx mcpxyz
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
HYPERLIQUID_PRIVATE_KEYConfiguration, not credentials: ALLOWED_ASSETS, ENV_FILE, HYPERLIQUID_MCP_SHOW_LOGS, HYPERLIQUID_TESTNET, HYPERLIQUID_USER_ADDRESS, VALIDATE_ASSET, XYZ_DEX
Where it talks to
no vendor host named in the codeAlso hyperliquid-testnet.xyz — 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 hyperliquid-testnet.xyz as well as its own vendor. The guard injects HYPERLIQUID_PRIVATE_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx mcpxyz

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-11 and scored it 86/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

HIGH
Access to sensitive file pathsscripts/validate_testnet.py:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files2. Export env (or put in .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 pathsscripts/place_order.py:4 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesReads config from .env. Intended for TESTNET (HYPERLIQUID_TESTNET=true) with aFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/validate_testnet.py:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load config from a gitignored .env.testnet (keeps the key out of shell history).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/mcp_xyz/__init__.py:3 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load a local .env (if present) at import time so the server picks up configFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/place_order.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesload_dotenv(os.getenv("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 pathsscripts/validate_testnet.py:29 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesload_dotenv(os.getenv("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 pathsscripts/place_order.py:35 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint("ABORT: need READ_ONLY=false and an API wallet key in .env.")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
≈68 tok
1 file · 44 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 mcpxyz@0.4.0 as of 3d ago. This is the package itself, not its dependencies.