webhook-verify
Related Servers
Alternatives to webhook-verify
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to authenticate and route webhooks from Shopify, Stripe, GitHub, Slack, and PayPal using HMAC-SHA256 constant-time verification and timestamp replay-window validation. It then multiplexes verified events into agent workflows without external runtime dependencies.7MIT
- AlicenseNot gradedqualityBmaintenanceAn 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.7MIT
- AlicenseNot gradedqualityBmaintenanceWebhook management and debugging. Validate signatures, log events, replay, and analyze webhook traffic.52 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables secure ingestion and validation of payment webhooks using HMAC-SHA256 signatures, replay tolerance, and atomic idempotency locking to prevent duplicate financial transactions. It provides deterministic ledger integrity and risk auditing for autonomous financial agents and payment rails.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables verifying event-driven webhook signatures and providing HMAC replay protection for AI agents and MCP clients.8-
- AlicenseNot gradedqualityBmaintenanceEnables agents to cryptographically verify JWT HMAC-SHA256 signatures, validate claims and enforce expiration, and perform Merkle inclusion proofs, Schnorr zero-knowledge identification, and nonce replay protection. Runs as a zero-dependency stdio MCP server so clients like Claude Desktop, Cursor, and Windsurf can attest execution state without OpenSSL or external libraries.7MIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another. The tool's purpose is fully specified and self-contained, leaving no ambiguity about when to invoke it.
The tool name follows a clear verb_noun convention with snake_case, which is consistent and predictable. Even though there is only one tool, the pattern aligns with common standards and leaves no room for stylistic mismatch.
The server is purpose-built for webhook signature verification, and one focused tool is exactly the right scope. There is no unnecessary bloat, and the single tool fully addresses the server's intended functionality without feeling thin.
The tool covers the entire lifecycle of webhook verification: timing-safe comparison, replay protection, and detailed failure reasons. No additional tools appear needed for the stated purpose, making the surface complete for its domain.