Skip to main content
Glama
zhookteam

zhook-mcp-server

by zhookteam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to zhook-mcp-server

No user-submitted related servers found.

    Related Servers

    • hooklens

      aniruddhaadak80
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create webhook bins, list and retrieve captured requests, inspect payloads with seal-chain verification, and clear bins via MCP tools.
      4 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
      3 npm
      MIT

    • Hookbase MCP Server

      HookbaseApp
      A
      license
      A
      quality
      A
      maintenance
      Exposes the Hookbase webhook relay API as tools for AI assistants to manage sources, destinations, routes, and events through natural language. It enables monitoring webhook success rates, replaying failed deliveries, and managing localhost tunnels for development.
      32
      18 npm
      MIT
    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

    A3.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources (hooks, destinations, transformations, events, metrics) and actions (create, get, list, delete, update, trigger, wait). There is no overlap or ambiguity; for example, get_hook retrieves configuration while get_hook_metrics focuses on real-time metrics, and list_events is separate from get_event.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as create_destination, list_hooks, and update_transformation. The naming is predictable and uniform across all 18 tools, with no deviations in style or convention.

    Tool Count4/5

    With 18 tools, the count is slightly high but reasonable for a webhook management server covering hooks, destinations, transformations, events, and metrics. It provides comprehensive coverage without being excessive, though it borders on the upper limit of a well-scoped set.

    Completeness5/5

    The tool set offers complete CRUD/lifecycle coverage for the domain: hooks (create, get, list, trigger, wait), destinations (create, get, list, update, delete), transformations (create, get, list, update, delete), events (list, get), and metrics (real-time and aggregated). There are no obvious gaps, and agents can manage the full workflow from setup to monitoring.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources