A
licenseA
qualityD
maintenanceWebhook management and testing tools for AI agents. Provides tools for sending, validating, generating, and debugging webhooks.
5
32 npm
MIT
zhook-mcp-server
by zhookteam
Related Servers
Alternatives to zhook-mcp-server
No user-submitted related servers found.
Related Servers
- 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.43 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.59 npmMIT
- AlicenseNot gradedqualityBmaintenanceA webhook management and delivery service with MCP tools for endpoints, deliveries, relay, and incoming webhooks, enabling autonomous agents to send, track, and relay webhooks.MIT
- AlicenseAqualityAmaintenanceExposes the Hookbase webhook relay API as tools for AI assistants to manage sources, destinations, routes, and events through natural language. It enables monitoring webhook success rates, replaying failed deliveries, and managing localhost tunnels for development.32171 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.71MIT
TDQS
A3.5/5.0
Scored across 18 tools
Disambiguation5/5
Every tool has a clearly distinct purpose targeting specific resources (hooks, destinations, transformations, events, metrics) and actions (create, get, list, delete, update, trigger, wait). There is no overlap or ambiguity; for example, get_hook retrieves configuration while get_hook_metrics focuses on real-time metrics, and list_events is separate from get_event.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case, such as create_destination, list_hooks, and update_transformation. The naming is predictable and uniform across all 18 tools, with no deviations in style or convention.
Tool Count4/5
With 18 tools, the count is slightly high but reasonable for a webhook management server covering hooks, destinations, transformations, events, and metrics. It provides comprehensive coverage without being excessive, though it borders on the upper limit of a well-scoped set.
Completeness5/5
The tool set offers complete CRUD/lifecycle coverage for the domain: hooks (create, get, list, trigger, wait), destinations (create, get, list, update, delete), transformations (create, get, list, update, delete), events (list, get), and metrics (real-time and aggregated). There are no obvious gaps, and agents can manage the full workflow from setup to monitoring.
Maintenance
ActivityInactive
ResponsivenessNo issues