Webhook.site MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Sets the logging level for the server (e.g., DEBUG, INFO, WARNING, ERROR). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_webhookA | Create a disposable inbox to sign up on a website: HTTP URL, temp email, DNS. |
| create_webhook_with_configA | Create a webhook that returns a custom status, body, timeout, CORS, or alias. |
| send_to_webhookA | POST JSON to the webhook URL to test that capture works. Use when the user wants to send a sample payload, not when they are waiting for a real site or email. |
| get_webhook_requestsA | List captured HTTP, email, or DNS events for a webhook. |
| search_requestsA | Search captured events by method, body text, headers, type, or date. |
| get_latest_requestA | Return only the newest captured event (HTTP, email, or DNS). |
| get_webhook_infoA | Show webhook settings, expiry, and how many requests it has received. Use when the user asks if a token is still valid or how it is configured. |
| update_webhookB | Change how an existing webhook responds (status, body, timeout, CORS). |
| delete_webhookA | Permanently delete a webhook and every captured request/email. Use when the user is done with a temp inbox or wants to clean up. |
| delete_requestA | Delete one captured HTTP, email, or DNS event by request id. |
| delete_all_requestsB | Clear captured events on a webhook, optionally by date or search query. Use to reset an inbox before a new sign-up or test run. |
| get_webhook_urlA | Return https://webhook.site/{token} for an existing webhook. |
| get_webhook_emailA | Return the temp inbox to sign up, verify, magic-link, or reset a password. |
| get_webhook_dnsA | Return the DNSHook domain for an existing webhook. |
| wait_for_requestA | Poll until a new HTTP (or DNS) callback hits the webhook (1-120s). |
| wait_for_emailA | Wait for a sign-up, verify, magic-link, or password-reset email (1-120s). |
| follow_email_linkA | Open the verify / magic-link / reset URL from a captured sign-up email. |
| generate_ssrf_payloadB | Build authorized SSRF callback URLs that ping this webhook. |
| check_for_callbacksA | See if SSRF, XSS, or canary callbacks arrived in the last N minutes. |
| generate_xss_callbackA | Build authorized XSS payloads that ping this webhook when they run. |
| generate_canary_tokenA | Make a canary URL, DNS name, or email that alerts when someone opens it. |
| extract_links_from_requestA | Pull confirm, reset, magic-link, and other URLs from a captured email or HTTP body. |
| send_multiple_requestsA | POST several sample JSON payloads to the webhook, optionally spaced out. Use to load-test capture, not to wait for a real site or email. |
| export_webhook_dataA | Full dump of captured HTTP/email/DNS events, including HTML and untruncated bodies. Use this when list/wait tools omitted HTML or truncated a body. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Every tool has a clearly defined purpose with explicit guidance on when to use it. Overlaps like get_latest_request vs get_webhook_requests are disambiguated in descriptions, and security tools are separate from email/webhook tools.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_webhook, delete_request, wait_for_email). Security payload generators use generate_ prefix, and check_for_callbacks fits the pattern. No mixed conventions.
24 tools is on the higher side but justified by the broad scope: webhook lifecycle, email capture, DNS, request management, and security testing. Each tool earns its place, though some could theoretically be merged without much loss.
The surface covers the full lifecycle: create, configure, send, retrieve, wait, export, update, delete, search, and security payload generation. No obvious gaps for the stated purpose of webhook testing and temporary inbox functionality.