Three.ws Signals MCP Server

Three.ws Signals is an MCP integration. Discover signal feeds ranked by proven edge, rank publishers, and subscribe + track results.

Packages and local setup

The published npm package is @three-ws/signals-mcp, version 0.1.2. Its declared MCP transport is stdio.

The package declares THREE_WS_BASE: Base URL of the three.ws API that serves the signal-marketplace endpoints. Override only when self-hosting or targeting a preview deployment.; THREE_WS_TIMEOUT_MS: Per-request timeout in milliseconds for the live marketplace reads and subscription writes.; THREE_WS_API_KEY: three.ws API key (sk_live_… / sk_test_…) for the account-scoped follower tools (get_subscriptions, subscribe_signal, set_subscription_status). Optional — the public discovery and leaderboard tools work without it. subscribe_signal in live mode spends real USDC, so treat this key like cash..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.