Webhook (zebbern) MCP Server

webhook-mcp-server PyPI v3.0.0

Published by zebbern — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP Server for webhook.site API integration with layered architecture

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Dynamic code execution in server code (services/bugbounty_service.py)MTC-SRC-001

In the server's implementation (`services/bugbounty_service.py:260`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: s["base64"] = f'<script>eval(atob("{self._base64_encode(encoded_fetch)}"))</script>' payloads["unicode"] = self.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server services/bugbounty_service.py

high Shell/command execution in server code (evals/run_evals.py)MTC-SRC-002

In the server's implementation (`evals/run_evals.py:75`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: del", model] proc = subprocess.run(cmd, cwd=ROOT, capture_output=True, text=True, encoding="utf-8", errors="replace"

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server evals/run_evals.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([download_request_file]) co-exist with external-action tools ([create_webhook, configure_webhook, delete_webhook, export_webhook_data]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_request_file] → sinks [create_webhook, configure_webhook, delete_webhook, export_webhook_data]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow download_request_file → create_webhook

Tools 31

Each tool and what it can reach — statically extracted from the published source.

  • configure_webhooknetwork egress
  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • download_request_fileingests untrusted input
  • export_webhook_datanetwork egress
  • check_for_callbacksno sensitive capability
  • delete_all_requestsno sensitive capability
  • delete_requestno sensitive capability
  • extract_links_from_requestno sensitive capability
  • follow_email_linkno sensitive capability
Show 21 more tools ↓
  • generate_oob_payloadsno sensitive capability
  • get_requestno sensitive capability
  • get_webhook_emailno sensitive capability
  • get_webhook_infono sensitive capability
  • get_webhook_requestsno sensitive capability
  • list_webhooksno sensitive capability
  • manage_custom_actionsno sensitive capability
  • manage_databasesno sensitive capability
  • manage_global_variablesno sensitive capability
  • manage_groupsno sensitive capability
  • manage_queuesno sensitive capability
  • manage_schedulesno sensitive capability
  • manage_templatesno sensitive capability
  • manage_usersno sensitive capability
  • respond_to_next_requestno sensitive capability
  • search_requestsno sensitive capability
  • send_requestsno sensitive capability
  • server_statusno sensitive capability
  • update_requestno sensitive capability
  • wait_for_emailno sensitive capability
  • wait_for_requestno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.0.0 latest A 93/100 3 1.13.0 2026-09-04
v2.2.2 A 93/100 1 1.13.0 2026-08-25
v2.1.3 A 93/100 1 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/webhook-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/webhook-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/webhook-mcp-server"><img src="https://mcptrustchecker.com/registry/webhook-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/webhook-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan webhook-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Webhook 6

Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →

More in Developer Tools