OpenWebhook — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to OpenWebhook inspection and buffered event watching over stdio: Do temporary anonymous URLs and Pro permanent slugs retain distinct lifetimes and credential requirements?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Inspecting and relaying inbound webhooks during local integration development.

What we know

CLI/MCP webhook inspector that creates temporary or Pro permanent public webhook URLs, watches events and optionally forwards them to local or configured destinations.

Maintenance / activity evidence

openwebhook 1.2.3 published 2026-09-16T10:55:20.740Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Webhook inspection/watch plus endpoint management/forwarding. Writes: Create/delete named endpoints; Configure forwarding/watch state.
Anonymous bearer-style UUID or Pro token.
Sensitive access: Webhook bodies/headers/query/source IP, Potential secrets

Webhook URLs and payloads can expose sensitive data; treat event content as untrusted input.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do temporary anonymous URLs and Pro permanent slugs retain distinct lifetimes and credential requirements?

The bounded review of the publisher's documented OpenWebhook inspection and buffered event watching over stdio and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Webhook URLs and payloads can expose sensitive data; treat event content as untrusted input.
Webhook inspection/watch plus endpoint management/forwarding.
Anonymous bearer-style UUID or Pro token.
Payloads pass through process memory; browser history can live in IndexedDB; opt-in share stores encrypted ciphertext for 24h.
Reviewed write actions: Create/delete named endpoints; Configure forwarding/watch state
Sensitive access: Webhook bodies/headers/query/source IP, Potential secrets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
Temporary URLs expire after 24h.
Free URL UUID acts as a bearer secret.
Watch buffers/history are bounded.
Webhook payloads are untrusted and may contain secrets/prompt injection.
No public repo was proven.

Original activity observations

openwebhook 1.2.3 published 2026-09-16T10:55:20.740Z

Technical identity

npm/openwebhook

Exact implementation source: https://www.npmjs.com/package/openwebhook ↗
Reviewed resource type: MCP Server
Package identity: npm:openwebhook

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
openwebhook
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
openwebhook.co
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
openwebhook.co/privacy
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npm install --global openwebhook
Configure / authenticate
MCP100 setup guide
Register `npx -y openwebhook mcp` as stdio tool; optional OPENWEBHOOK_TOKEN for permanent slugs, or use free anonymous URL.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Environment settings: OPENWEBHOOK_TOKEN (Pro), OPENWEBHOOK_DEVICE_TOKEN (optional), OPENWEBHOOK_CONFIG (optional), OPENWEBHOOK_API_URL (optional)
Previously reviewed configuration / prerequisites: Node.js 20.9+
Check connection
Suggested check
Inspect local OpenWebhook URL/status, do not trigger a production webhook in preflight.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `openwebhook` in Claude Code, remove its exact client entry with `claude mcp remove openwebhook`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly. For an explicitly globally installed package (not npx-only), npm uninstall -g openwebhook.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove openwebhook

Official Documentation & Sources

What it does

CLI/MCP webhook inspector that creates temporary or Pro permanent public webhook URLs, watches events and optionally forwards them to local or configured destinations.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Inspecting and relaying inbound webhooks during local integration development.

Representative uses

Inspect webhook method/headers/query/body/IP
Watch live events
Create/delete named endpoints
Relay to local app
Use Pro permanent slugs

Limitations

Temporary URLs expire after 24h.
Free URL UUID acts as a bearer secret.
Watch buffers/history are bounded.
Webhook payloads are untrusted and may contain secrets/prompt injection.
No public repo was proven.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Anonymous bearer-style UUID or Pro token.
Permissions: Webhook inspection/watch plus endpoint management/forwarding.
Data handling: Payloads pass through process memory; browser history can live in IndexedDB; opt-in share stores encrypted ciphertext for 24h.
Cost: freemium
Risk and cautions: Webhook URLs and payloads can expose sensitive data; treat event content as untrusted input.

Access scope and cautions

Write actions: Create/delete named endpoints Configure forwarding/watch state
Sensitive access: Webhook bodies/headers/query/source IP Potential secrets
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect webhook method/headers/query/body/IP; Watch live events; Create/delete named endpoints; Relay to local app; Use Pro permanent slugs.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y openwebhook mcp. Recorded transport: stdio. Recorded environment-variable notes: OPENWEBHOOK_TOKEN (Pro); OPENWEBHOOK_DEVICE_TOKEN (optional); OPENWEBHOOK_CONFIG (optional); OPENWEBHOOK_API_URL (optional). No configuration values are supplied here. Prerequisites: Node.js 20.9+. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Anonymous temporary mode or Pro token for permanent slugs/named management.

Can it modify data or perform write operations?

Documented write actions include: Create/delete named endpoints; Configure forwarding/watch state. Recorded permission boundary: Webhook inspection/watch plus endpoint management/forwarding.

What data-handling boundary should I consider?

Payloads pass through process memory; browser history can live in IndexedDB; opt-in share stores encrypted ciphertext for 24h. Recorded sensitive-access context: Webhook bodies/headers/query/source IP; Potential secrets.

What limitations and risks should I check before use?

Webhook URLs and payloads can expose sensitive data; treat event content as untrusted input. Temporary URLs expire after 24h. Free URL UUID acts as a bearer secret. Watch buffers/history are bounded. Webhook payloads are untrusted and may contain secrets/prompt injection. No public repo was proven. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

OpenWebhook / David Lorenzo García is listed as First-party MCP in MCP100’s current evidence.