io.github.rog0x/webhook
NPM · @ROG0X/MCP-WEBHOOK-TOOLS · SCANNED SEP 20
Send, validate, debug webhooks for AI agents
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 181 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 630 tokens (~126/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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; "webhook_send" 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 5 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
How do I install the io.github.rog0x/webhook MCP server?
io.github.rog0x/webhook runs locally as an npm package, launched with npx -y @rog0x/mcp-webhook-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-webhook-tools
claude mcp add rog0x-webhook -- npx -y @rog0x/mcp-webhook-tools
{
"mcpServers": {
"rog0x-webhook": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-webhook-tools"
]
}
}
} {
"servers": {
"rog0x-webhook": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-webhook-tools"
]
}
}
} codex mcp add rog0x-webhook -- npx -y @rog0x/mcp-webhook-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-webhook": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-webhook-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-webhook --command npx --arg -y --arg @rog0x/mcp-webhook-tools
mcp_servers:
rog0x-webhook:
command: "npx"
args: ["-y", "@rog0x/mcp-webhook-tools"] {
"McpServers": {
"rog0x-webhook": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@rog0x/mcp-webhook-tools"
]
}
}
} assistant mcp add rog0x-webhook -t stdio -c npx -a -y @rog0x/mcp-webhook-tools
{
"mcpServers": {
"rog0x-webhook": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-webhook-tools"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@rog0x/mcp-webhook-tools@1.0.2
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
webhook_debug ~96
Analyze a webhook request: parse headers, validate signature, decode body, check content-type, verify timestamp freshness, and detect the provider.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Raw request body |
| headers | object | yes | Request headers as key-value pairs |
| method | string | – | HTTP method used |
| secret | string | – | Signing secret for signature verification (optional) |
| url | string | – | The webhook endpoint URL (for reference) |
No output schema declared.
No examples provided.
webhook_generate_payload ~93
Generate a realistic webhook payload for common services. Supports Stripe (payment_intent.succeeded), GitHub (push, pull_request), and Slack (message).
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | Event type (e.g., payment_intent.succeeded, push, pull_request, message) |
| overrides | object | – | Optional field overrides to merge into the generated payload |
| service | string | yes | Service to generate payload for |
No output schema declared.
No examples provided.
webhook_retry_schedule ~135
Calculate a retry schedule with exponential backoff and optional jitter. Shows the delay, cumulative time, and scheduled timestamp for each retry attempt.
| Name | Type | Req | Description |
|---|---|---|---|
| base_delay_ms | number | – | Initial delay in milliseconds (default: 1000) |
| jitter | boolean | – | Add randomized jitter (default: true) |
| max_delay_ms | number | – | Maximum delay cap in milliseconds (default: 60000) |
| max_retries | number | yes | Number of retry attempts |
| multiplier | number | – | Backoff multiplier (default: 2) |
| start_time | string | – | ISO 8601 start time (default: now) |
No output schema declared.
No examples provided.
webhook_send ~160
Send a webhook payload to a URL with custom headers, body, and content-type. Supports retry with exponential backoff.
| Name | Type | Req | Description |
|---|---|---|---|
| base_delay_ms | number | – | Base delay between retries in ms (default: 1000) |
| body | string | yes | Request body (typically JSON string) |
| content_type | string | – | Content-Type header (default: application/json) |
| headers | object | – | Custom HTTP headers as key-value pairs |
| max_retries | number | – | Maximum retry attempts on failure (default: 0) |
| method | string | – | HTTP method (default: POST) |
| timeout_ms | number | – | Request timeout in milliseconds (default: 10000) |
| url | string | yes | Target URL to send the webhook to |
No output schema declared.
No examples provided.
webhook_validate ~146
Validate a webhook signature. Supports HMAC-SHA256 and HMAC-SHA1 with built-in patterns for Stripe, GitHub, and Slack.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Hash algorithm (default: sha256) |
| payload | string | yes | The raw webhook payload body |
| provider | string | – | Webhook provider for automatic format detection |
| secret | string | yes | The webhook signing secret |
| signature | string | yes | The signature to validate |
| signature_format | string | – | Signature encoding (default: hex) |
| timestamp | string | – | Request timestamp (required for Slack) |
| tolerance_seconds | number | – | Max age of timestamp in seconds (default: 300) |
No output schema declared.
No examples provided.
What is the io.github.rog0x/webhook MCP server?
io.github.rog0x/webhook is an MCP server listed in the public MCP registry as io.github.rog0x/webhook. Send, validate, debug webhooks for AI agents. This page covers its npm package (@rog0x/mcp-webhook-tools).
Is the io.github.rog0x/webhook MCP server safe to use?
io.github.rog0x/webhook scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.rog0x/webhook MCP server expose?
io.github.rog0x/webhook exposes 5 tools: webhook_send, webhook_validate, webhook_generate_payload, webhook_debug, webhook_retry_schedule. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.
Is the io.github.rog0x/webhook MCP server still maintained?
io.github.rog0x/webhook is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.rog0x/webhook MCP server under?
io.github.rog0x/webhook declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.