Skip to main content
Glama

Server Details

Webhook capture bins for agents: get a URL, wait for webhooks, set replies, verify signatures.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct action—create bin, read/list/wait for captures, simulate a delivery, configure a response, and verify a signature. The reading tools are differentiated by listing summaries vs. retrieving full captures vs. blocking for the next arrival, so agents should not misselect.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern: create_bin, get_capture, list_captures, set_response, verify_signature. Multi-word targets and wait_for are still predictable and match the same imperative style.

Tool Count5/5

Seven tools cover the webhook capture workflow without redundancy or bloat. Each tool serves a concrete stage in the create → capture → inspect → respond → verify loop, which is an ideal scope for an MCP server.

Completeness4/5

The core lifecycle is well covered: bins can be created, captures can be listed/read/waited for, test webhooks can be generated, responses configured, and signatures verified. Minor gaps exist around bin lifecycle management—there is no list_bins/get_bin/delete_bin or capture deletion—but auto-expiring anonymous bins make this a workable, not blocking, omission.

Available Tools

7 tools
create_binAInspect

Create a new webhook capture bin. Returns a public capture_url — point any webhook (Stripe, GitHub, Slack, your own service…) at it and every request sent there (any method, any subpath, headers + raw body) is stored. Then read what arrived with list_captures, get_capture, or wait_for_capture. Anonymous bins keep requests ~24h. No auth needed.

Inputs: no named parameters.

get_captureAInspect

Get one captured request in full: method, path, query, every header, and the body. Binary bodies are returned base64-encoded (up to 8KB, with a URL for the raw bytes).

Inputs: id (required), bin (required).

list_capturesAInspect

List requests captured by a bin, oldest first. Compact summaries (id, method, path, time, content-type, body size, signature status). Use get_capture for full headers/body. Pass after (a capture id) to only see newer captures.

Inputs: bin (required), after, limit.

send_test_webhookAInspect

Simulate a webhook delivery into a bin — no external sender or HTTP client needed. Seeds one realistic, clearly-labeled sample capture (default: a GitHub push event) and returns it in full, so you can exercise the whole loop (create_bin → send_test_webhook → list_captures / get_capture) entirely from MCP. Pass example to pick a provider payload from the /examples library (e.g. "stripe-payment-intent-succeeded", "slack-event-callback", "shopify-order-created"). Sample captures are marked as simulated and never count as real webhook traffic.

Inputs: bin (required), example.

set_responseAInspect

Configure what a bin replies to webhook senders: HTTP status, content-type, body, custom response headers, optional delay. Body and header values support {{…}} templates rendered per-request from the INCOMING delivery — {{body.challenge}}, {{query.hub.challenge}}, {{header.x-hook-secret}}, {{hmac_sha256 body.plainToken YOUR_SECRET}} — so a bin can pass provider verification handshakes with zero code: Slack URL verification (body {{body.challenge}}), Zoom CRC (JSON with the hmac_sha256 helper), Meta/WhatsApp GET echo (text/plain {{query.hub.challenge}}), Strava (JSON {"hub.challenge":"{{query.hub.challenge}}"}), Asana (response header X-Hook-Secret: {{header.x-hook-secret}}). Only the fields you pass change; everything else keeps its current value. Works on bins created via create_bin by this same client; the incoming request is still captured in full either way.

Inputs: bin (required), body, status, headers, +2 more.

verify_signatureAInspect

Verify a webhook signature against a secret — 25 provider-exact schemes plus a generic HMAC mode, the same engine that computes ✓/✗ badges on captures. Covers HMAC-SHA256 (GitHub, Stripe, Svix/Standard Webhooks, Shopify-style base64, URL-signing Square/HubSpot/Trello…), ECDSA (SendGrid), RSA (Kick) and HMAC-MD5 (Patreon). Pass the scheme, the secret, the delivery's headers, and the BYTE-EXACT raw body (body_base64 for binary). The secret is used only for this one in-memory computation — never stored or logged. No bin needed. If verification fails, the #1 cause is a re-serialized body: point the real webhook at a capture bin (create_bin) to get the true raw bytes first.

Inputs: scheme (required), secret (required), url, body, +4 more.

wait_for_captureAInspect

Block until the next request arrives at a bin (or a timeout passes), then return it in full. Ideal flow: create_bin → configure the webhook sender → trigger it → wait_for_capture. If after_id is omitted, waits for the next capture after "now". Returns timed_out:true instead of erroring when nothing arrives.

Inputs: bin (required), after_id, timeout_seconds.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources