Skip to main content
Glama
pipepie

pipepie

Official
by pipepie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to pipepie

No user-submitted related servers found.

    Related Servers

    • elsba3ei Webhook MCP Server

      elsba3ei
      A
      license
      Not graded
      quality
      B
      maintenance
      A high-performance local and public webhook inspector for testing SSRF, APIs, and out-of-band interactions with Cloudflare Quick Tunnel, dynamic mocks, and callback polling for AI agents.
      1
      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

    • Universal MCP Gateway

      Samuel-Mencke
      F
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP gateway that aggregates all your MCP servers behind a single Streamable HTTP endpoint, with automatic registry discovery (19,000+ servers), on-demand Docker provisioning, multi-device support via SSH, OAuth2 PKCE authentication, and a workflow engine for saving and replaying multi-step tool sequences.
      -

    • LivePort MCP

      dundas
      F
      license
      Not graded
      quality
      D
      maintenance
      Give AI agents access to your localhost dev server. Zero-config tunnel that works with Claude Code, OpenClaw, and any MCP-compatible agent. No interstitial pages, no account required.
      -
    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.9/5.0

    Scored across 13 tools

    Disambiguation4/5

    Tools are largely distinct with clear purposes, though 'active_tunnels', 'list_tunnels', and 'tunnel_status' all relate to tunnel visibility and could cause momentary hesitation. The separation between 'create_tunnel' (registration) and 'connect' (session establishment) is well-defined.

    Naming Consistency3/5

    Mixed naming conventions detract from consistency: 'connect', 'disconnect', and 'overview' use single-word verbs/nouns while others use verb_noun patterns ('create_tunnel', 'inspect_request'). 'active_tunnels' and 'pipeline_traces' use adjective_noun or noun_noun patterns, making the set feel somewhat fragmented despite being readable.

    Tool Count5/5

    Thirteen tools is well-suited for this domain, covering tunnel lifecycle (create/connect/disconnect/delete), request inspection (list/inspect/replay), and pipeline debugging without bloat. Each tool serves a distinct operational need in the tunneling/webhook workflow.

    Completeness4/5

    Covers the full tunnel lifecycle and webhook inspection surface comprehensively, including useful debugging features like replay and pipeline tracing. Minor gap: no 'update_tunnel' for modifying existing tunnel configuration, though agents can work around this via delete/recreate if needed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources