MCP Events Bridge
OfficialRelated Servers
Alternatives to MCP Events Bridge
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables agents such as ChatGPT to subscribe to events happening behind an MCP server (for example, order.created with filters) and receive them as signed webhooks without the builder implementing delivery itself. Hookdeck Outpost handles filtering, Standard Webhooks signing, retries, and delivery to each subscriber's callback URL.MIT- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that authenticates incoming webhooks from multiple providers such as Shopify, Stripe, GitHub, Slack, and PayPal using HMAC-SHA256 constant-time verification and timestamp replay-window validation. It lets agents validate and multiplex verified webhook events into dispatched event streams.MIT
- AlicenseNot gradedqualityBmaintenanceEnables a publisher to POST JSON to a webhook endpoint in a private network and lets an AI agent list, fetch, or block-wait on those stored events over MCP. It also mints scoped webhook URLs and pages through retained events without deleting them.MIT
- AlicenseAqualityCmaintenanceLet AI agents operate your webhook gateway: inspect failed deliveries, read payloads, replay dropped events, and fire test webhooks.422 npmMIT
- AlicenseNot gradedqualityCmaintenanceA 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
- AlicenseAqualityDmaintenanceMCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.16MIT
TDQS
Scored across 7 tools
Each tool has a distinct role: source discovery, new-event polling, long-waiting, past-event listing, single-event lookup, and callback URL creation/listing. The closest pair, poll_events and wait_for_event, is clearly separated by immediate return versus blocking wait and cross-references in the descriptions.
All tool names follow a consistent snake_case verb_noun pattern: list_sources, poll_events, wait_for_event, create_callback_url, get_event, list_callback_urls, and list_events. There are no mixed conventions or vague names.
Seven tools is well-scoped for an event bridge: source discovery, event consumption via polling/waiting/past lookup, and callback URL support. Each tool earns its place without redundant surface area.
The core event-consumption lifecycle is covered: discover sources, poll or wait for new events, list past events, and retrieve an event by id. Callback URL management is slightly incomplete because URLs can be created and listed but not explicitly deleted, though they auto-expire after an hour.