push-notifications-mcpSAFE
Read and manage your three.ws notification inbox from any AI agent — list inbound events (pump/market alerts, sales, purchases, social, IRL, account), mark read, tune the per-category delivery matrix, and register Web Push devices. Account-scoped over the live API via a Bearer API key.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
@three-ws/notifications-mcp
Your three.ws notification inbox, delivery preferences, and Web Push devices — from any AI agent.
Install · Quick start · Tools · Authentication · Errors · three.ws
A Model Context Protocol server that gives an AI assistant its own three.ws notification inbox + delivery control over stdio. Read inbound events (pump/market alerts, sales & earnings, purchase receipts, social mentions, IRL interactions, account/security notices), mark them read, tune the per-category → per-channel delivery matrix, and register Web Push devices — all live, all account-scoped.
Why
An agent that trades, sells skills, or stands in the real world generates inbou
869fbf9e2bd6OBSERVED · 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 notifications-mcp --env THREE_WS_API_KEY=${THREE_WS_API_KEY} -- 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 (7)
.nojekyll
@modelcontextprotocol/sdk, zod
Every read and write hits the real three.ws API. The server is **authenticated**: it carries a three.ws API key (or OAuth access token) as a `Bearer` credential and resolves the owning account on ever
<p>Every read and write hits the real three.ws API. The server is <strong>authenticated</strong>: it carries a three.ws API key (or OAuth access token) as a <code>Bearer</code> credential and resolves
Every read and write hits the real three.ws API. The server is **authenticated**: it carries a three.ws API key (or OAuth access token) as a `Bearer` credential and resolves the owning account on ever
Every read and write hits the real three.ws API. The server is **authenticated**: it carries a three.ws API key (or OAuth access token) as a `Bearer` credential and resolves the owning account on ever
Gates applied: no_behavioural_pass.
869fbf9e2bd6full audit observations/trust-audit/mcp-server/nirholas__push-notifications-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 | 869fbf9e2bd6 | SAFE | B | 89 | first audit |
Questions
What is the push-notifications-mcp MCP server?
Read and manage your three.ws notification inbox from any AI agent — list inbound events (pump/market alerts, sales, purchases, social, IRL, account), mark read, tune the per-category delivery matrix, and register Web Push devices. Account-scoped over the live API via a Bearer API key.
Is push-notifications-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 push-notifications-mcp need?
It reads THREE_WS_API_KEY 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 push-notifications-mcp run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as @three-ws/notifications-mcp at 0.1.4.
How current is this page?
The grade is for one exact copy of the source (869fbf9e2bd6), read on 2026-10-10. The repository is watched and re-audited when it changes.