Sato Hub
Trading Tool

Purple Flea Trading

API and MCP server for trading 275+ perpetual futures (crypto, stocks, commodities, forex) on Hyperliquid.

  • Sato Score37
  • ChainsHyperliquid
EarlyUnverifiedQuiet · 7mo ago

Purple Flea Trading is an open-source trading tool on Hyperliquid, with last code activity on 2026-03-19 (Quiet). Sato Score 37/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install Purple Flea Trading →

Last commit Mar 19, 2026

Listed from purpleflea.com on 2026-07-19. Install: not attempted. Evidence →

Next step

Watch Purple Flea Trading

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on purple-flea/agent-trading before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Purple Flea Trading is a REST API and MCP server that lets an AI agent open and manage perpetual futures positions across crypto, equities, commodities, forex, and indices, executed on Hyperliquid with up to 50x leverage. An agent builder uses it to give an agent programmatic order placement, position management, and market data without a browser or manual KYC step.

Sato Score

37/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
5/35
Code transparency
16/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
10/15
Independent verification
0/10

Evidence — listed vs checked · what the words mean

Listed from purpleflea.com on 2026-07-19. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedHyperliquidself-reportedtrading.purpleflea.comas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedpurpleflea.comas of 2026-10-21
Recent activitylast commit 2026-03-19observedgithub.com/purple-flea/agent-trading2026-10-21
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reportedgithub.com/purple-flea/agent-tradingas of 2026-09-14
Website answersdid not answer our checkobservedpurpleflea.com2026-10-21
Daily check record0 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Deploys ashosted API, self-hostedconfidence 0.80self-reportedgithub.com/purple-flea/agent-tradingas of 2026-09-28
Sato Score37/100 (Low)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: Node.js (REST API server, NOT an MCP server per its own docs)

git clone https://github.com/purple-flea/agent-trading.git
cd agent-trading
npm install
npm run dev
npm run dev (dev, hot reload, http://localhost:3003) or npm start (production, compiled server)

You supply: ENCRYPTION_KEY (production only — AES-256-GCM secret used to encrypt stored Hyperliquid signing keys. RISK: handles user signing-key material server-side), PORT (optional, default 3003), TRADING_API_KEY (optional, per README described as 'API key for MCP server'), hl_wallet_address + hl_signing_key (required per-account via POST /v1/auth/register against the hosted API at trading.purpleflea.com — RISK: submits a Hyperliquid signing key to a third-party service)

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

0%of 51 checks since 2026-09-01 succeeded
Currently unreachable from our probe for 51 days
Succeeded
30
Failed
61
Their error
0
Unattributed
61

State changed on 2026-08-22 (responding → unclear), 2026-09-01 (unclear → unreachable from our probe).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
fewer than 2 points—
7-day rolling; unattributable days are gaps · 0/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
37
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Hyperliquid
Agent types
MCP server
Open source
Yes
Pricing
Volume-tiered fees (5.5 bps free tier)
Deploys as
hosted API, self-hosted
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#trading#perpetuals#mcp#hyperliquid#derivatives

Where Purple Flea Trading fits

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Purple Flea Trading's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 28, 2026
    Auto-enriched: deployment options, has pricing
  2. Sep 26, 2026
    Edited: entity class, resource type
  3. Sep 15, 2026
    Sato Score tier: Medium → Low
    Score 42 → 34.
  4. Jul 24, 2026
    Sato Hub began tracking this listing
  5. Jul 20, 2026
    Edited: deploy spec
  6. Jul 19, 2026
    Listed on Sato Hub

Compared with

Related Resources

Reference

QuestionsShowHide

Questions people ask about Purple Flea Trading

Is Purple Flea Trading open source?
Yes. Purple Flea Trading is open source under the MIT license; the repository is https://github.com/purple-flea/agent-trading. Checked as of 2026-10-21.
Which chains does Purple Flea Trading support?
Purple Flea Trading lists support for Hyperliquid as of 2026-10-21.
Is Purple Flea Trading still maintained?
The most recent code activity Sato Hub observed was on 2026-03-19 (last commit 2026-03-19), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Purple Flea Trading?
Node.js (REST API server, NOT an MCP server per its own docs). Install: git clone https://github.com/purple-flea/agent-trading.git && cd agent-trading && npm install && npm run dev. Entry: npm run dev (dev, hot reload, http://localhost:3003) or npm start (production, compiled server). This is taken from the project's own documentation and has not been reproduced by Sato Hub.
Is Purple Flea Trading verified on Sato Hub?
No independent verification is on record for Purple Flea Trading; its verification status is "Unverified" and its Sato Score is 37 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Purple Flea Trading — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/purple-flea-trading

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.