Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"agentping": {
"url": "https://ping.mgm-llc.org/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A hosted, remote MCP server. One tool: send_notification.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'wrangler' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Wrangler affected by OS Command Injection in `wrangler pages deploy`
**Summary** A command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. **Root cause** The `commitHash` variable, derived from user input via the `--commit-hash` CLI argument, is interpolated directl
Arbitrary remote code execution within `wrangler dev` Workers sandbox
### Impact The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. `wrangler dev` would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate `Origin`/`Host` headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability
Arbitrary remote file read in Wrangler dev server
### Impact Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file. ### Patches This issue was fixed in `wrangler@3.19.0`. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps. ### Workarounds Configure Wr
Cloudflare Wrangler directory traversal vulnerability
### Impact The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server. ### Patches Wrangler2: Upgrade to v2.20.1 or higher. Wrangler3: Upgrade to v3
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Compact, efficient, and extensible long-term memory for LLM agents.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Noriget/agentping and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Let your AI agent notify you — by email, Slack, Discord, or webhook.
A hosted, remote MCP server. One tool: send_notification.
Website · Docs · Get an API key (free)
▶ Get your free API key → ping.mgm-llc.org/signup
Long-running agents work while you're away. AgentPing gives them a send_notification tool so they can reach you the moment something matters:
Notifications go to any channel you configure: email, Slack, Discord, or a custom webhook.
🔒 Read-only by design. AgentPing can only send the notifications your agent triggers. It has no access to your inbox, files, or accounts.
A. Remote URL — Cursor and any client that supports Streamable HTTP:
{
"mcpServers": {
"agentping": {
"url": "https://ping.mgm-llc.org/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
B. Stdio bridge — works with every MCP client (incl. Claude Desktop):
{
"mcpServers": {
"agentping": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ping.mgm-llc.org/mcp", "--header", "Authorization: Bearer YOUR_API_KEY"]
}
}
}
Get your API key by signing up at ping.mgm-llc.org and setting your destinations. See the full docs for per-client steps and Slack/Discord webhook setup.
| Tool | Arguments | Notes |
|---|---|---|
send_notification | title (string, required), message (string, optional), channel (optional) | channel ∈ all | email | slack | discord | webhook. Default: all configured channels. |
Stateless Streamable HTTP (JSON-RPC 2.0): initialize, tools/list, tools/call, ping. Auth via Authorization: Bearer <api_key> (or ?key= for clients that can't set headers).
Built on Cloudflare Workers + D1 + Hono. To run your own instance:
npm install
npm run db:local
npm run dev # http://localhost:8787
.dev.vars needs APP_SECRET (and RESEND_API_KEY to enable email).
npx wrangler login
npx wrangler d1 create agentping # put database_id in wrangler.jsonc
npm run db:remote
npx wrangler secret put APP_SECRET
npx wrangler secret put RESEND_API_KEY
# Stripe billing (optional):
npx wrangler secret put STRIPE_SECRET_KEY
npx wrangler secret put STRIPE_WEBHOOK_SECRET
npx wrangler deploy
Set vars.APP_URL to the production URL and attach a custom domain.
MIT · Operated by MGM LLC.