A
licenseA
qualityB
maintenanceEnables LLM agents to create, read, update, and delete Webhook.site tokens, list and retrieve captured requests, and manage webhook configurations via the Webhook.site API.
7
1
MIT
Webhook.site MCP Server
by zebbern
Related Servers
Alternatives to Webhook.site MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceWebhook management and testing tools for AI agents. Provides tools for sending, validating, generating, and debugging webhooks.529 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables management and inspection of webhook tokens (URLs) and incoming requests via webhook-test.com, allowing users to create, list, fetch details, fetch payloads, and delete webhooks without custom API integrations.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create webhook URLs, wait for incoming deliveries, inspect payloads, and replay or send signed webhook events to a local handler.314 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to create disposable webhook URLs, capture incoming HTTP requests, inspect headers and bodies, and replay them against local or remote endpoints, streamlining the webhook handler development loop.53 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables generating webhook endpoints for testing, inspecting and comparing HTTP request payloads, replaying requests from history, and forwarding requests to localhost.2MIT
TDQS
A4/5.0
Scored across 24 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness5/5
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.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive