World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Description from the maker (original English)
Send yourself a push notification from an AI assistant. No account, one environment variable.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
WEBHOOKY_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"webhooky": {
"command": "npx",
"args": [
"-y",
"webhooky-mcp"
],
"env": {
"WEBHOOKY_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add webhooky --env WEBHOOKY_URL=your-value -- npx -y webhooky-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"webhooky": {
"command": "npx",
"args": [
"-y",
"webhooky-mcp"
],
"env": {
"WEBHOOKY_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"webhooky": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"webhooky-mcp"
],
"env": {
"WEBHOOKY_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified with the GitHub account MatthiasMAigner, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: WEBHOOKY_URL
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, Claude Flow, Tldraw
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Gives an AI assistant one ability: send a push notification to your phone. Useful when you ask it to do something long-running and then walk away, it can tell you itself instead of writing code that tells you.
You: Run the migration and let me know when it's done.
Claude: [runs it, then calls send_notification] 📱 ✅ Migration done · 14,203 rows · 6m12s
Install the Webhooky app (iOS · Android), create an endpoint and copy its URL. No account needed, the URL exists the moment the app opens. The free plan covers 100 notifications per month across up to 3 endpoints.
claude mcp add webhooky -e WEBHOOKY_URL=https://api.webhooky.app/YOUR_KEY -- npx -y webhooky-mcp
Add to claude_desktop_config.json:
{
"mcpServers": { "webhooky": { "command": "npx", "args": ["-y", "webhooky-mcp"], "env": { "WEBHOOKY_URL": "https://api.webhooky.app/YOUR_KEY" } } } }
Same shape: command npx, args ["-y", "webhooky-mcp"], and WEBHOOKY_URL in the environment.
send_notification| Argument | Type | Required | Notes |
|---|---|---|---|
title | string | yes | Max 100 characters |
message | string | no | Max 500 characters. Omit to use the endpoint's configured text |
sound | enum | no | One of the 40 sound ids. Omit to use the endpoint's sound |
vibrate | boolean | no | Overrides the endpoint's vibration setting |
Returns a confirmation including how many devices it reached. It reports an error, rather than a cheerful success, when the notification was accepted but not delivered, which is what happens when the free plan's monthly quota is used up. Webhooky answers HTTP 200 in that case on purpose, so that senders like Stripe don't retry, and this server unpacks that distinction for you.
list_soundsThe 40 sounds grouped by meaning (money, success, failure, informational, attention-grabbing, playful), so the assistant can pick one that matches the event instead of guessing from an id.
| Variable | Required | Default | Notes |
|---|---|---|---|
WEBHOOKY_URL | yes | (none) | Your full endpoint URL, key included |
WEBHOOKY_TIMEOUT_MS | no | 10000 | Request timeout |
WEBHOOKY_URL must be https, except on localhost / 127.0.0.1, where plain http is allowed because nothing leaves the machine.
Your endpoint URL can do exactly one thing: trigger a notification on your phone. It cannot read your history, reach your account or expose any data. Anyone who knows it can send you notifications, and that is the whole blast radius. This server therefore takes it only from the environment, never as a tool argument: a model can't be talked into sending to a different endpoint, and the key never enters the conversation. It is also stripped from any error message before it is returned.
Treat WEBHOOKY_URL the way you would a Slack incoming webhook URL: keep it out of public repositories, but it is not a password. If it leaks, delete the endpoint in the app and create a new one. The old URL dies instantly.
npm install
npm test # drives the server over real stdio against a stub endpoint
MIT · Aigner Software e.U.