three.ws Activity
io.github.nirholasPublished by GitHub account nirholasv0.1.3Updated Oct 24, 2026
Trending agents and coins, the $THREE holder leaderboard, and the site-wide activity ticker.
Overview
A local stdio MCP server that lets an assistant read live three.ws discovery data: trending agents and coins, the $THREE holder leaderboard, tiers, and the site
- What you can do
- Read trending agents ranked by chat activity over 24h, 7d or all time, optionally sorted by wallet-trust reputation, with limits up to 20. Read trending coins ranked by the Oracle's conviction score with sub-scores. Read the $THREE holder leaderboard by on-chain balance, with tiers, a market strip and an optional wallet standing lookup. Read the holder tier ladder with labels and minimum balances. Read the site-wide activity ticker of coin buys, agent deploys, level-ups and payments, newest first.
- When to use it
- Useful when someone wants an assistant to report what is currently trending on three.ws, check where a wallet sits on the $THREE holder board, or summarize recent platform activity. It is a read-only discovery surface, not a trading or wallet tool.
- Requirements
- Node.js 20 or newer, run locally via npx or npm install. Network access to the three.ws API. Optional environment variables THREE_WS_BASE (defaults to the public site) and THREE_WS_TIMEOUT_MS (default 20000). No API key or account.
Installation
In SourceWeft
- Open three.ws Activity 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/activity-mcp
What's hot on three.ws right now — trending agents and coins, the $THREE holder leaderboard with tiers, and the site-wide activity ticker, from any AI agent.
[npm] [license] [node] [MCP Registry] [three.ws]
A Model Context Protocol server that gives any AI assistant the three.ws live discovery surface over stdio. See which agents are trending by real chat activity, which coins the Oracle has the highest conviction in, where a wallet sits on the $THREE holder leaderboard, what each holder tier means, and what's happening across the platform right now — all live, read-only, no key required.
Every ranking, tier, and event comes straight from the public three.ws API. No API key, no signer, no payment — point THREE_WS_BASE at a deployment and go.
Install
Or run with npx (no install):
Quick start
Claude Code, one line:
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
Inspect the surface with the MCP Inspector:
Tools
All five tools read live data: rankings, the holder board, and the feed all move between calls, so none are idempotent.
Input parameters
get_trending_agents — window (24h | 7d | all, default 24h), sort (activity | trust, default activity), limit (1–20, default 10).
get_trending_coins — limit (1–20, default 10).
get_holder_leaderboard — limit (1–100, default 50), offset (default 0), wallet (optional base58 — adds the wallet's own you standing).
get_tier_info — no parameters.
get_feed_events — limit (1–100, default 30).
Example
The $THREE holder leaderboard is for $THREE — the only coin three.ws ranks holders for (CA FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump). The trending-coins list is the platform's runtime launch-directory discovery data: a ranking of what the Oracle scored, never a recommendation of any coin.
Requirements
- Node.js >= 20.
- Network access to
https://three.ws(or your ownTHREE_WS_BASE).
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/activity-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