Skip to main content
Glama
rog0x

mcp-webhook-tools

by rog0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-webhook-tools

No user-submitted related servers found.

    Related Servers

    • webhook-ai-mcp

      CSOAI-ORG
      F
      license
      Not graded
      quality
      B
      maintenance
      Webhook management and debugging. Validate signatures, log events, replay, and analyze webhook traffic.
      64 PyPI
      -

    • Webhook.site MCP Server

      zebbern
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with Webhook.site to create, manage, and monitor endpoints for capturing HTTP requests, emails, and DNS lookups. It provides 16 tools for testing webhooks and inspecting incoming data through the Model Context Protocol.
      24
      109 PyPI
      12
      MIT

    • hookray-mcp

      ShotaTanikawa
      A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      5
      4 npm
      MIT

    • Webhook Tester MCP Server

      mikeysrecipes
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables management and inspection of webhook tokens (URLs) and incoming requests via webhook-test.com, allowing users to create, list, fetch details, fetch payloads, and delete webhooks without custom API integrations.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct webhook operation: generating payloads, sending, validating signatures, debugging requests, and computing retry schedules. No two tools overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent 'webhook_<verb>_<noun>' pattern in snake_case. Clear and predictable naming convention throughout.

    Tool Count5/5

    Five tools is well-scoped for a webhook utility server. Each tool serves a distinct need without redundancy or bloat.

    Completeness5/5

    The set covers the core webhook workflow: generate, send, validate, debug, and plan retries. There are no obvious missing operations for the server's stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources