Skip to main content
Glama
kroqdotdev

webhooks-cc

by kroqdotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to webhooks-cc

No user-submitted related servers found.

    Related Servers

    • hookshelf-mcp

      vinkurov
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • korb by korb-sh

      korbofficial

      korb-sh
      A
      license
      A
      quality
      B
      maintenance
      Let AI agents operate your webhook gateway: inspect failed deliveries, read payloads, replay dropped events, and fire test webhooks.
      4
      112 npm
      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
      7 npm
      MIT

    • webhook-ai-mcp

      CSOAI-ORG
      A
      license
      Not graded
      quality
      B
      maintenance
      Webhook management and debugging. Validate signatures, log events, replay, and analyze webhook traffic.
      51 PyPI
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool maps to a distinct resource and action: endpoint CRUD, request retrieval, and account connection are cleanly separated. The two wait tools (wait_for_connection vs wait_for_request) and the account/sandbox split could momentarily confuse, but descriptions make the boundaries explicit.

    Naming Consistency4/5

    Nearly all tools follow a clear verb_noun pattern (create_endpoint, list_requests, get_request, delete_endpoint, generate_payload_schema). The lone exception is about_sandbox, which is a noun-style informational tool rather than verb_noun.

    Tool Count4/5

    Eleven tools is well-scoped for a webhook capture service: sandbox lifecycle, request inspection, schema generation, and account onboarding each have dedicated tools. about_sandbox is arguably redundant with descriptions but is harmless and explicitly offline.

    Completeness4/5

    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: no per-request deletion or endpoint update/config tools within the sandbox surface, though those appear to require an account.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources