Skills/Glama/hydromancer-mcp

hydromancer-mcp@r1

VERIFIED· not started

Publisher claims: "Provides read-only access to the Hydromancer Hyperliquid API, letting AI apps query wallets, trades, top traders, markets, funding rates, order-book depth and liquidations in plain English. All requests go to the read-only /info endpoint, so it never places orders or handles funds or keys." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher joshavenue · publishing for 16 daysInstalls 0Last detonated 3d ago
$npx skills add hydromancer-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
HYDROMANCER_API_KEYConfiguration, not credentials: HYDROMANCER_BASE_URL, HYDROMANCER_MAX_RESULT_CHARS
Where it talks to
hydromancer.xyz (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 HYDROMANCER_API_KEY and talks to hydromancer.xyz. 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 HYDROMANCER_API_KEY=hydromancer.xyz -- <the server's command>

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

Is hydromancer-mcp@r1 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-12 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 · 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

MEDIUM
URL with embedded credentialstests/test_client.py:246 · URL with embedded credentials — may be phishing or credential leaking"https://user:[email protected]/info",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST07
MEDIUM
Python subprocess execution detectedtests/test_live.py:101 · Python subprocess execution detectedproc = subprocess.run([sys.executable, str(script)], capture_output=True, text=True, timeout=120)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Privileged sudo command.github/workflows/snap.yml:33 · Privileged sudo command — agent may execute with elevated privilegessudo snap install --dangerous "$SNAP_FILE"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈42 tok
1 file · 25 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

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.