Skip to main content
Glama
Sign In
SlingHook

SlingHook

by DylanCourtney584
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to SlingHook

No user-submitted related servers found.

    Related Servers

    • stripe-webhook-mcp

      3598644
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to capture, inspect, and replay Stripe webhook events into a local handler with valid signatures, returning the handler's status and body so agents can debug failures directly.
      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
      8 npm
      MIT
    • korb

      korbofficial

      korb-sh
      A
      license
      A
      quality
      C
      maintenance
      Let AI agents operate your webhook gateway: inspect failed deliveries, read payloads, replay dropped events, and fire test webhooks.
      4
      14 npm
      MIT

    • hookshelf-mcp

      vinkurov
      A
      license
      Not graded
      quality
      C
      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
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool pairs a distinct action with a distinct object: listing endpoints/scenarios/events, reading a single event, comparing events, debugging a signature, replaying one event, running a scenario, and fetching a replay result. The only cluster with any risk is replay_event vs run_scenario vs get_replay_result, and the descriptions sharply separate perform-one, perform-sequence, and read-history. An agent can select correctly without guessing.

    Naming Consistency5/5

    Every name follows the same snake_case verb_noun convention (list_endpoints, get_event, replay_event, debug_signature, generate_handler, compare_events, create_endpoint). The verbs map predictably to the action performed and resource names are reused consistently across list/get/create.

    Tool Count5/5

    Eleven tools map cleanly onto the workflow stages of capturing, inspecting, replaying, and debugging webhooks, with no filler tools. Each entry earns its place without inflating the surface.

    Completeness4/5

    Coverage is strong for the agent's core loop: discover endpoints, list/get/compare events, debug signatures, replay, verify fixes, and generate handler scaffolding. Gaps (no delete or rename endpoint, no event deletion, secrets intentionally dashboard-only) are deliberate and manageable from the dashboard rather than agent dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources