Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Webhooky

NPM · WEBHOOKY-MCP · 2 COMPONENTS

Send yourself a push notification from an AI assistant. No account, one environment variable.

+15 this week 70 Trust /100

Last scanned (4 minutes ago)

Scores higher than 41% of npm servers

Category Communication

Trust breakdown (7 categories)

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 → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 209 tokens (~104/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_notification" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 18 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 17 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 +16
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • Package version: 1.0.3 → 1.0.5 functional
    • Package version: 1.0.3 → 1.0.4 functional
  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 24

    First indexed and scored.

Diagnostics

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 22 Nov 2026 · Analysed npm/webhooky-mcp@1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~209 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_sounds ~38

List the notification sounds a Webhooky endpoint can play, grouped by what they mean. Call this before send_notification when unsure which sound fits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

send_notification ~171

Send a push notification to the user's phone via their Webhooky endpoint. Use this to tell the user something finished, succeeded or failed when they are away from the screen. Pick a sound that matches the meaning: cash_register for revenue, level_up_2 for success, buzzer or error_1 for failure, notification_1 when it is merely informational. Call list_sounds for the full set.

NameTypeReqDescription
messagestring–Notification body, max 500 characters. Omit to use the endpoint's configured text.
soundstring–Sound id. Omit to use the sound configured on the endpoint.
titlestringyesNotification title, max 100 characters. Keep it scannable.
vibrateboolean–Override the endpoint's vibration setting for this notification.

No output schema declared.

No examples provided.

Install

How do I install the Webhooky MCP server?

Webhooky runs locally as an npm package, launched with npx -y webhooky-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · webhooky-mcp

# add to Claude Code
claude mcp add matthiasmaigner-webhooky-mcp -- npx -y webhooky-mcp
Common questions

What is the Webhooky MCP server?

Webhooky is an MCP server listed in the public MCP registry as io.github.MatthiasMAigner/webhooky-mcp. Send yourself a push notification from an AI assistant. No account, one environment variable. This page covers its npm package (webhooky-mcp).

Is the Webhooky MCP server safe to use?

Webhooky scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Webhooky MCP server expose?

Webhooky exposes 2 tools: send_notification, list_sounds. Their descriptions and schemas cost roughly 209 tokens of context every time the server is loaded.

Is the Webhooky MCP server still maintained?

Webhooky is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Webhooky MCP server under?

Webhooky declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Webhooky MCP server?

VerifyMCP ran 15 checks on Webhooky, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Webhooky: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.