{"id":"webhook-mcp-server","name":"webhook-mcp-server","af_score":51.2,"security_score":43.2,"reliability_score":26.2,"what_it_does":"Provides an MCP (Model Context Protocol) server that wraps webhook.site capabilities: creating and managing webhook endpoints (HTTP), and retrieving captured HTTP requests, emails, and DNS lookups. It also exposes tools for waiting/polling for new events and for generating common security test payloads (e.g., SSRF/XSS canary-style artifacts) and exporting captured data.","best_when":"You want an agent-friendly interface (MCP tools via stdio) to quickly create webhook.site endpoints and programmatically capture/inspect resulting HTTP/email/DNS events for testing and debugging.","avoid_when":"You require explicit, documented security controls for access to stored captures; you also want formal pagination/idempotency/retry guarantees beyond what’s documented in the README.","last_evaluated":"2026-04-04T21:39:31.875020+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["Because the MCP server likely wraps an external SaaS (webhook.site), agent workflows may depend on webhook token state and eventual arrival of requests/emails/DNS lookups; the README emphasizes waiting/polling but does not document timeout/retry semantics or race conditions.","Security-related helper tools (SSRF/XSS/canaries) can generate payloads that may cause unintended network interaction; agents should still enforce strict safety/authorization checks externally.","The README documents many tools, but it does not show formal tool schemas, parameter constraints, or example error responses; agents may need to handle unexpected tool failures or external-service errors."],"error_quality":0.0}