swaphunt-mcp@0.7.0
VERIFIED· not startedPublisher claims: "MCP server with 30 SwapHunt crypto market tools for AI agents (Hyperliquid prices, regime, volatility, funding, coin strength, anti-FOMO sanity checks; Fear & Greed), paid per call in USDC via x402, plus a free local prediction market fee calculator (Kalshi, Polymarket)" 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: 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
PRIVATE_KEYPRIVATE_KEY_FILEConfiguration, not credentials: MAX_SPEND_USD, PAYTO_ALLOWLIST, SWAPHUNT_API_URL, X402_PAY- Where it talks to
- swaphunt.dev (its own)Also githubusercontent.com, basescan.org — 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 githubusercontent.com, basescan.org as well as its own vendor. The guard injects PRIVATE_KEY, PRIVATE_KEY_FILE only into requests to swaphunt.dev (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.
What changed since 0.4.1
vet-skills diff swaphunt-mcp 0.4.1 0.7.0This version reaches for something 0.4.1 did not: 3 new hosts (basescan.org, githubusercontent.com, swaphunt.dev) · 2 new credential variables (PRIVATE_KEY, PRIVATE_KEY_FILE). Compared from the two recorded runs, not from source.
- New hosts
- basescan.org, githubusercontent.com, swaphunt.dev
- New credential variables
- PRIVATE_KEY, PRIVATE_KEY_FILE
0.4.1 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 88/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 deviationsStatic findings
ICON_URL = "https://raw.githubusercontent.com/swaphunt/x402-examples/main/mcp-server/assets/icon-512.png"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.No other findings across 1,200 lines in 8 files.
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.