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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_webhookA | Create a new webhook.site endpoint. Returns the unique token/URL for the webhook. |
| create_webhook_with_configB | Create a new webhook.site endpoint with custom configuration (response content, status, timeout, CORS, alias). |
| send_to_webhookC | Send a POST request with JSON data to a webhook.site endpoint. |
| get_webhook_requestsC | Get all requests that have been sent to a webhook.site endpoint. |
| search_requestsB | Search requests sent to a webhook with query filters (method, content, headers, date range, type). |
| get_latest_requestB | Get the most recent request sent to a webhook.site endpoint. |
| get_webhook_infoC | Get detailed information about a webhook (settings, expiry, stats). |
| update_webhookC | Update webhook settings (response content, status code, timeout, CORS). |
| delete_webhookB | Delete a webhook.site endpoint and all its data. |
| delete_requestB | Delete a specific request from a webhook. |
| delete_all_requestsB | Delete all requests from a webhook, optionally filtered by date range or query. |
| get_webhook_urlA | Get the full URL for a webhook token. Optionally validate that the token exists. |
| get_webhook_emailA | Get the unique email address for a webhook token. Any emails sent to this address will be captured by the webhook. Optionally validate that the token exists. |
| get_webhook_dnsA | Get the unique DNSHook domain for a webhook token. Any DNS lookups to this domain (or subdomains) will be captured. Useful for bypassing firewalls or as canary tokens. Optionally validate that the token exists. |
| wait_for_requestB | Wait for a new HTTP request to be received by the webhook. Uses real-time streaming (SSE) to efficiently wait without polling. Useful for testing webhooks, callbacks, and API integrations. |
| wait_for_emailA | Wait for an email to be received at the webhook's email address ({token}@email.webhook.site). Uses real-time streaming (SSE) to efficiently wait. Automatically extracts links from the email, including magic/auth links for login flows. |
| generate_ssrf_payloadB | Generate SSRF (Server-Side Request Forgery) test payloads for bug bounty testing. Creates unique identifiable URLs that can be injected into targets to detect blind SSRF vulnerabilities. |
| check_for_callbacksA | Quick check if any OOB (Out-of-Band) callbacks have been received. Useful for bug bounty to verify if SSRF, XXE, or blind injection payloads were triggered. |
| generate_xss_callbackA | Generate XSS (Cross-Site Scripting) callback payloads for bug bounty testing. Creates JavaScript payloads that ping your webhook when executed, useful for detecting blind XSS. |
| generate_canary_tokenA | Generate canary tokens for detecting unauthorized access or data leakage. Creates trackable URLs that alert you when accessed. |
| extract_links_from_requestA | Extract and analyze all URLs/links from a captured request. Useful for finding password reset links, verification tokens, and other sensitive URLs. |
| send_multiple_requestsA | Send multiple requests to a webhook in batch. Useful for load testing or sending multiple test payloads at once. |
| export_webhook_dataA | Export all captured requests from a webhook to JSON format. Includes full request details: headers, body, IP, timestamp, user agent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zebbern/webhook-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server