Skip to main content
Glama
gba3124

anyhook-mcp

by gba3124
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to anyhook-mcp

No user-submitted related servers found.

    Related Servers

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      44 npm
      8
      MIT

    • kiln

      danielyayla
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides coding agents with fully-contextualized work orders from a knowledge graph, enabling them to retrieve and update work order status.
      4 npm
      MIT

    • mcp-gauge

      sogawa-yk
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables coding agents to autonomously test, evaluate, and tune other MCP servers by acting as a proxy and providing linting, trace recording, evaluation, comparison, and reporting tools.
      7
      MIT

    • ScopeGate

      NexgenSystemsMX
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides ephemeral credentials and persistent MCP connections for AI coding agents, enabling secure access to services like GitHub and AWS without exposing secrets to the agent.
      10 npm
      Apache 2.0
    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.8/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct lifecycle stages (create, list, inspect, replay, verify, mock), and descriptions clearly delineate summary vs detail and local vs remote. A few pairs overlap—replay/replay_failed and mock/simulate—but the descriptions are explicit enough that an agent can pick correctly.

    Naming Consistency3/5

    All names share an anyhook_ prefix and avoid camelCase, but the grammatical pattern is inconsistent: verbs (replay, inspect, mock), nouns (events, providers, inbox), adjectives (undelivered), and noun-first compounds (apps_create, apps_list) are mixed. This is readable but not predictable enough to infer an unlisted tool's name.

    Tool Count5/5

    Thirteen tools is squarely in the well-scoped range and maps to distinct steps in the webhook workflow: bootstrap/create, list/inspect, replay/verify/mock. None feel like filler, and the count supports a coherent utility without bloating the surface.

    Completeness4/5

    Core webhook lifecycle is covered: creating endpoints, listing events, inspecting payloads, replaying failed deliveries, mocking providers, and verifying signatures. Missing app/destination update/delete operations (PATCH is mentioned in a description but no tool exists) are the main gap, though they are work-aroundable via other tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources