webhooks-cc
Related Servers
Alternatives to webhooks-cc
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.546 npmMIT
- 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.49 npmMIT
- AlicenseAqualityBmaintenanceLets AI coding agents list captured webhooks, explain why a signature failed, replay events to localhost and generate handler code. Works with Stripe, GitHub, Shopify, Slack and Twilio.11527 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents to receive and inspect real webhook payloads locally, send signature-valid test events for seven providers, and replay deliveries — all without leaving the machine.MIT
- AlicenseAqualityCmaintenanceLet AI agents operate your webhook gateway: inspect failed deliveries, read payloads, replay dropped events, and fire test webhooks.422 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.56 npmMIT
TDQS
Scored across 11 tools
Request tools (list/get/wait) and endpoint tools (create/list/get/delete) are clearly separated by resource and action. The only mild overlap is between about_sandbox, connect_account, and wait_for_connection, which all touch the account story, but their descriptions make the distinction clear (informational vs. initiate vs. poll).
Nearly all tools follow a consistent snake_case verb_noun pattern (list_requests, get_endpoint, delete_endpoint, generate_payload_schema, connect_account). The lone deviation is about_sandbox, which is a noun phrase rather than a verb_noun, but it remains readable and unambiguous.
Eleven tools is well within the ideal 3-15 range and each tool maps to a distinct operation in the sandbox webhook workflow. No tool feels redundant or padded.
Endpoint lifecycle (create/list/get/delete) and request inspection (list/get/wait) are fully covered, plus schema generation and an account-upgrade path. Minor gaps exist—no way to clear/delete individual captured requests or update an endpoint—but these are workable around given the sandbox's auto-expiry.