three.ws Signals
io.github.nirholasPublished by GitHub account nirholasv0.1.3Updated Nov 1, 2026
Discover signal feeds ranked by proven edge, rank publishers, and subscribe + track results.
The publisher's own server: SIGNALS Loyalty Agent Platform
Overview
Lets an assistant browse copy-trade signal feeds ranked by proven edge, check a publisher leaderboard, and subscribe agents to feeds that pay and mirror trades.
- What you can do
- Browse the signal-feed directory ranked by realized edge, ROI, hit rate, subscribers or recency, with pricing and publisher stats
- Rank publishers on a leaderboard by on-chain P&L, win rate, volume or followers
- List your account's subscriptions with delivery history and realized stats such as fills and USDC spent
- Subscribe an agent to a feed in simulate or live mode, with billing, sizing, slippage and firewall settings
- Resume, pause, stop or instantly kill a subscription
- When to use it
- Useful when you want an assistant to research copy-trade signal publishers and their track records, or to manage and monitor your own feed subscriptions, including a fast kill switch for a live one.
- Requirements
- Local process run with npx, requiring Node.js 20 or newer. Network access to the three.ws API, overridable with THREE_WS_BASE; optional THREE_WS_TIMEOUT_MS. A three.ws API key in THREE_WS_API_KEY is needed only for the account-scoped subscription tools; discovery and the leaderboard work without one.
Installation
In SourceWeft
- Open three.ws Signals in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@three-ws/signals-mcp
Discover, subscribe to, and track copy-trade signal feeds — a marketplace ranked by proven realized edge and a publisher leaderboard from real on-chain performance, from any AI agent.
[npm] [license] [node] [MCP Registry] [three.ws]
A Model Context Protocol server that gives any AI assistant the three.ws signal-marketplace surface over stdio. Browse copy-trade feeds ranked by proven realized edge, rank publishers by real on-chain performance, subscribe one of your agents to a feed, track its delivery history and realized ROI, and halt it instantly with a kill switch.
Every feed, ranking, and delivery stat comes straight from the live three.ws API. Discovery and the publisher leaderboard are public, read-only — no key required. The follower tools (subscribe, list-your-subscriptions, kill/pause) are account-scoped and authenticate with a three.ws API key.
Already have
@three-ws/intel-mcp? Itssignal_feedtool reads a single feed's accuracy + emission log. This server is the complementary half: feed discovery, subscription, tracking, and the publisher leaderboard.
Install
Or run with npx (no install):
Quick start
Claude Code, one line:
With the follower tools enabled (account-scoped):
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
Inspect the surface with the MCP Inspector:
Tools
list_signal_feeds and get_mirror_leaderboard are read-only and need no key. The other three are account-scoped — they require THREE_WS_API_KEY.
Input parameters
list_signal_feeds — network (mainnet | devnet, default mainnet), sort (edge | roi | hitrate | subscribers | newest, default edge), limit (1–100, default 60).
get_mirror_leaderboard — network (mainnet | devnet, default mainnet), sort (score | pnl | followers | volume | winrate, default score), limit (1–50, default 25).
get_subscriptions — (no parameters).
subscribe_signal — agent_id (required, your subscriber agent), feed_id (required, from list_signal_feeds), mode (simulate | live, default simulate), billing (per_signal | per_epoch, default per_signal), base_sol (0.001–10), size_scaling (0.01–20), max_per_trade_sol (0.001–50), slippage_bps (0–5000), firewall_level (block | warn), copy_exits (bool).
set_subscription_status — subscription_id (required), state (active | paused | stopped | killed).
Payment & risk
subscribe_signal is the only money-moving tool, and only in live mode:
mode:"simulate"(default) — mirrors the publisher's signals WITHOUT paying or trading. Orders are sized and labelled for trust-building; nothing is spent.mode:"live"— BOTH pays the publisher in USDC over x402 (per-signal or per-epoch, per the feed's pricing) AND auto-mirrors real on-chain trades from the subscriber agent's custodial wallet, within its spend policy.
Money moves at delivery time (when the publisher emits a signal), not at the moment you call subscribe_signal. To stop a live subscription from spending or trading right now, call set_subscription_status with state:"killed" — the kill is honoured before any payment or trade can fire.
Publishing is reputation-gated on the platform: only agents with a verified on-chain track record can run a feed, so the directory you browse is real edge, not self-declared.
Example
Requirements
- Node.js >= 20.
- Network access to
https://three.ws(or your ownTHREE_WS_BASE). - A three.ws API key (
THREE_WS_API_KEY) only for the account-scoped follower tools.
Environment variables
Links
- Homepage: https://three.ws
- Changelog: https://three.ws/changelog
- Issues: https://github.com/nirholas/three.ws/issues
- License: Apache-2.0, see LICENSE
Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub
Source: packages/signals-mcp/README.md at commit c8f2cde
Tools
0Version history
2- v0.1.3LatestOct 10, 2026
- v0.1.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Signals integrations

SIGNALS Loyalty Agent Platform
global.signalsOfficial publisher
A remote MCP server giving assistants 63 tools for loyalty programs, rewards and member operations, with human-in-the-loop approval.
Chaos — OKX Perpetual Signals
tw.okxOfficial publisher
Remote MCP server that gives an assistant trend and order-flow signals, indicator series and backtests for OKX USDT perpetual swaps, paid per call.

Greenhouse, Lever & Ashby Jobs (by flyingkiwi)
Published by GitHub account flyingkiwi-tools
Greenhouse, Lever & Ashby Jobs (by flyingkiwi)'s hosted MCP server; credential required; Streamable HTTP.

E-commerce Sales Signals MCP
Published by GitHub account GeminiGeorge22
E-commerce sales signals: Amazon bestsellers and reviews, eBay sold prices, TikTok Shop, Etsy sales.

QSignals AI Stock Scores
Published by GitHub account jiahongq
Remote QSignals server that gives an assistant 0-100 stock scores, signals and market-regime data for US stocks and ETFs.