Skip to main content
Glama
zebbern

Webhook.site MCP Server

by zebbern

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNoSets 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_webhookA

Create a disposable inbox to sign up on a website: HTTP URL, temp email, DNS.

    Use this first when the user wants to sign up, receive a verification /
    magic-link / password-reset email, catch a webhook callback, or get a
    one-off URL. Returns token, url, email ({token}@email.webhook.site),
    and dns. Next: give the email or URL to the site, then wait_for_email,
    then follow_email_link or use the OTP.
    
create_webhook_with_configA

Create a webhook that returns a custom status, body, timeout, CORS, or alias.

    Use when the user wants the endpoint to pretend to be an API (404, delay,
    JSON body) instead of a default 200. For a normal sign-up inbox, use
    create_webhook.
    
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.

    Use to inspect what already arrived. Bodies are truncated and HTML is
    omitted; use export_webhook_data for the full dump. For the newest item
    use get_latest_request. To wait for something new use wait_for_request
    or wait_for_email. Filter emails with request_type='email'.
    
search_requestsA

Search captured events by method, body text, headers, type, or date.

    Use when the user asks to find POSTs, a keyword, or only emails/DNS.
    Examples: query='method:POST', query='content:verify', request_type='email'.
    
get_latest_requestA

Return only the newest captured event (HTTP, email, or DNS).

    Use for a quick peek. Prefer wait_for_email after a sign-up, or
    get_webhook_requests to see history.
    
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).

    Use after create_webhook when the user wants a different canned reply.
    
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.

    Use when the user already has a token and needs the HTTP callback URL.
    For a new inbox, create_webhook already returns url.
    
get_webhook_emailA

Return the temp inbox to sign up, verify, magic-link, or reset a password.

    Address is {token}@email.webhook.site. Use when the user already has a
    token. If they do not, call create_webhook first — it also returns
    email. After the site sends mail, call wait_for_email.
    
get_webhook_dnsA

Return the DNSHook domain for an existing webhook.

    Use for out-of-band DNS callbacks, not for sign-up email. create_webhook
    already returns dns.
    
wait_for_requestA

Poll until a new HTTP (or DNS) callback hits the webhook (1-120s).

    Use after giving a site the webhook URL. Bodies are truncated and HTML
    is omitted; use export_webhook_data for the full dump. For verification
    / magic-link / password-reset mail, use wait_for_email instead. Set
    return_existing=true if the request may already be there.
    
wait_for_emailA

Wait for a sign-up, verify, magic-link, or password-reset email (1-120s).

    Call this after the user (or you) submitted {token}@email.webhook.site
    on a website. Returns subject, a truncated text preview, extracted
    confirm / reset / login URLs, and verification_codes (OTP). Next:
    follow_email_link, or type the code. HTML is omitted; use
    export_webhook_data for the full message. Set return_existing=true if
    the email already arrived. If there is no token yet, create_webhook first.
    
follow_email_linkA

Open the verify / magic-link / reset URL from a captured sign-up email.

    Use after wait_for_email. Only follows http(s) links already in that
    inbox. Returns status, final URL, and a short page preview. For OTP
    codes, read verification_codes from wait_for_email instead.
    
generate_ssrf_payloadB

Build authorized SSRF callback URLs that ping this webhook.

    Use only on systems you are allowed to test — not for sign-up email.
    Confirm hits with check_for_callbacks. local_bypass_examples cannot
    be confirmed here.
    
check_for_callbacksA

See if SSRF, XSS, or canary callbacks arrived in the last N minutes.

    Use after generate_ssrf_payload / generate_xss_callback / generate_canary_token.
    For a website verification email, use wait_for_email.
    
generate_xss_callbackA

Build authorized XSS payloads that ping this webhook when they run.

    Use only on systems you are allowed to test. Confirm with check_for_callbacks.
    
generate_canary_tokenA

Make a canary URL, DNS name, or email that alerts when someone opens it.

    Use to mark your own files or systems. token_type='email' is a tripwire,
    not a sign-up inbox — use create_webhook + wait_for_email for that.
    
extract_links_from_requestA

Pull confirm, reset, magic-link, and other URLs from a captured email or HTTP body.

    Use after wait_for_email or get_webhook_requests when the user needs
    the verification / login / password-reset link or OTP. Defaults to the
    latest event. wait_for_email already extracts links and codes.
    
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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