alerts-mcpSAFE
Manage your three.ws pump.fun alert rules from any AI agent — create, update, and delete monitoring rules with in-app, webhook, and Telegram delivery, and read the fired-alert history. Account-scoped over the live API.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
@three-ws/alerts-mcp
Run your own pump.fun monitoring from any AI agent — define alert rules, deliver them in-app / by signed webhook / to Telegram, and read the fired-alert history.
A Model Context Protocol server that turns the three.ws pump.fun alerts surface into an agent-drivable control plane over stdio. Define rules on pump.fun events — graduations, market-cap crossings, whale buys, new launches — and let the three.ws cron evaluate them against the live event stream and deliver across in-app, webhook, and Telegram. Read back what actually fired, with per-channel delivery health.
Rules are account-scoped: every call carries your three.ws session, so the server reads and writes only your rules and your alert history. The pumpfun-monitor cron does the watching server-side, so your rules fire across devices with no dashboard open.
Install
npm install @three-ws/alerts-mcp
Or run with npx (no install):
npx @three-ws/alerts-mcp
Quick start
Claude Code, one line:
claude mcp add alerts -e THREE_WS
3c98d52f7ee0OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add alerts-mcp --env THREE_WS_SESSION=${THREE_WS_SESSION} -- npx -y @three-ws/[email protected]Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
.nojekyll
@modelcontextprotocol/sdk, zod
Gates applied: no_behavioural_pass.
3c98d52f7ee0full audit observations/trust-audit/mcp-server/nirholas__alerts-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 3c98d52f7ee0 | SAFE | B | 89 | first audit |
Questions
What is the alerts-mcp MCP server?
Manage your three.ws pump.fun alert rules from any AI agent — create, update, and delete monitoring rules with in-app, webhook, and Telegram delivery, and read the fired-alert history. Account-scoped over the live API.
Is alerts-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does alerts-mcp need?
It reads THREE_WS_SESSION from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does alerts-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @three-ws/alerts-mcp at 0.1.3.
How current is this page?
The grade is for one exact copy of the source (3c98d52f7ee0), read on 2026-10-10. The repository is watched and re-audited when it changes.