three.ws Alerts
NPM · @THREE-WS/ALERTS-MCP · SCANNED AUG 3
Create, update, and delete pump.fun alert rules and read fired-alert history across channels.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 29 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1607 tokens (~321/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @three-ws/alerts-mcp
claude mcp add nirholas-alerts-mcp -- npx -y @three-ws/alerts-mcp
codex mcp add nirholas-alerts-mcp -- npx -y @three-ws/alerts-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-alerts-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/alerts-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-alerts-mcp --command npx --arg -y --arg @three-ws/alerts-mcp
mcp_servers:
nirholas-alerts-mcp:
command: "npx"
args: ["-y", "@three-ws/alerts-mcp"] {
"mcpServers": {
"nirholas-alerts-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/alerts-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +58
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: Apache-2.0 functional
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 −18
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 42
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@three-ws/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_alert_rule Create a pump.fun alert rule ~503
Create a pump.fun alert rule on the authenticated three.ws account. The pumpfun-monitor cron evaluates it against the live event stream and delivers across the channels you enable, so it fires across devices with no dashboard open. NOT idempotent — each call adds a new rule (max 50 per account). Targeting by kind: `graduation` is global or scoped to target_mint OR target_agent; `price_above` / `price_below` / `whale_buy` require target_mint; `new_mint` requires target_agent. `threshold` is required for the price/whale kinds — USD market cap for price_above/price_below, minimum buy size in SOL for whale_buy. At least one delivery channel must be on (deliver_in_app defaults true; webhook_url must be https and gets a generated webhook_secret for signature verification; telegram_chat is a numeric chat id or @username). Any mint you pass is runtime input — three.ws promotes only $THREE. Returns the created rule. Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| cooldown_seconds | integer | — | Minimum seconds between fires for this rule (5–86400, default 300). |
| deliver_in_app | boolean | — | Deliver as an in-app notification (default true). |
| enabled | boolean | — | Whether the rule is active (default true). |
| kind | string | yes | Event to watch: graduation | price_above | price_below | whale_buy | new_mint. |
| label | string | — | Optional human label; a default is derived from kind/target when omitted. |
| target_agent | string | — | three.ws agent UUID to watch. Required for new_mint; optional for graduation; forbidden for the mint-targeted kinds. |
| target_mint | string | — | Coin mint to watch. Required for price_above/price_below/whale_buy; optional for graduation; forbidden for new_mint. |
| telegram_chat | string | — | Telegram numeric chat id (e.g. 123456789) or @username to deliver to via the platform bot. |
| threshold | number | — | Required for price/whale kinds: USD market cap for price_above/price_below, minimum buy size in SOL for whale_buy. Ignored for graduation/new_mint. |
| webhook_url | string | — | HTTPS endpoint to POST a signed alert event to. The response includes a generated webhook_secret for verifying the webhook-signature header. |
No output schema declared.
No examples provided.
delete_alert_rule Delete a pump.fun alert rule ~124
Permanently delete a pump.fun alert rule by id from the authenticated three.ws account. DESTRUCTIVE and irreversible: the rule plus its cooldown tracker and per-channel delivery log are removed (cascade). The rule stops firing immediately. Deleting an already-deleted id returns not_found (so this is not idempotent). To pause a rule without losing it, prefer update_alert_rule with enabled:false. Returns the deleted rule id. Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | Id of the rule to delete (from list_alert_rules). This cannot be undone. |
No output schema declared.
No examples provided.
get_alert_history Read fired pump.fun alert history ~216
Read the pump.fun alerts that have actually fired for the authenticated account, newest first. Each entry carries a one-line `summary`, the originating `rule_id`, the event `kind`, the coin (mint / name / symbol), whether it has been `read`, when it `fired_at`, and the full `event` payload (amounts, market cap, tx signature, buyer, …). Pair this with list_alert_rules — whose `recent_deliveries` shows per-channel send outcomes — to see both what fired and how it was delivered. Optionally filter to one rule (rule_id) or one kind. The feed returns at most the 50 most recent alerts. Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | — | Only return alerts of this event kind. |
| limit | integer | — | Maximum number of fired alerts to return, newest first (1–50, default 20). |
| rule_id | string | — | Only return alerts fired by this rule id (matches the rule_id in each alert payload). |
No output schema declared.
No examples provided.
list_alert_rules List my pump.fun alert rules ~166
List every pump.fun alert rule on the authenticated three.ws account. Each rule has a `kind` (graduation | price_above | price_below | whale_buy | new_mint), its target (target_mint or target_agent), an optional numeric `threshold` (USD market cap for price rules, SOL for whale_buy), the delivery channels (deliver_in_app, webhook_url + webhook_secret, telegram_chat), the cooldown, and whether it is enabled. Also returns live delivery health: `last_fired_at`, `recent_failures` (failed channel deliveries in the last 24h), and `recent_deliveries` (the last few per-channel outcomes). Use this to audit what an agent is watching before creating or editing rules. Requires THREE_WS_SESSION.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_alert_rule Update a pump.fun alert rule ~412
Update an existing pump.fun alert rule by id on the authenticated three.ws account. Partial — only the fields you pass change. Idempotent: re-applying the same values yields the same rule. Common uses: flip `enabled` to pause/resume, retune `threshold`, add or swap a delivery channel, or change `kind` (the rule is re-validated against the new kind, and fields incompatible with it are cleared automatically). Pass null to clear a clearable field (target_mint, target_agent, threshold, webhook_url, telegram_chat, label). Removing webhook_url drops its secret; adding one mints a fresh webhook_secret (returned). The result must still have at least one delivery channel and satisfy the kind's targeting/threshold rules, or the API rejects it with a precise message. Returns the updated rule. Requires THREE_WS_SESSION.
| Name | Type | Req | Description |
|---|---|---|---|
| cooldown_seconds | integer | — | Minimum seconds between fires (5–86400). |
| deliver_in_app | boolean | — | Toggle in-app delivery. |
| enabled | boolean | — | Enable or pause the rule. |
| kind | string | — | Change the event kind. The rule is re-validated against it and incompatible fields are cleared. |
| label | — | — | Human label, or null to fall back to the derived default. |
| rule_id | string | yes | Id of the rule to update (from list_alert_rules). |
| target_agent | — | — | three.ws agent UUID to watch, or null to clear. Required by new_mint; forbidden for mint-targeted kinds. |
| target_mint | — | — | Coin mint to watch, or null to clear. Required by price/whale kinds; forbidden for new_mint. |
| telegram_chat | — | — | Telegram numeric chat id or @username, or null to remove. |
| threshold | — | — | USD market cap (price kinds) or SOL buy size (whale_buy), or null to clear. |
| webhook_url | — | — | HTTPS endpoint for signed alert events, or null to remove the webhook (and its secret). |
No output schema declared.
No examples provided.