Skip to main content
Glama

Related Servers

Alternatives to lowdown-proxy

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      VCR for MCP servers: a zero-dependency stdio proxy that records and replays MCP JSON-RPC tool calls to local cassette files, enabling deterministic, offline testing of AI agent workflows without side-effects or rate limits.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight stdio proxy that intercepts and rewrites MCP tool annotations to bypass security approval prompts in AI CLIs like Codex and Claude Code. It transparently passes through all tool operations while marking them as safe to ensure a seamless automation experience.
      12 npm
      10
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Exposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to drive a retrieval-grounded multi-agent workflow over stdio JSON-RPC, with journalled effects so recorded runs replay byte-for-byte from their trace. It also lets an agent answer retrieval by calling a tool on another MCP server.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables zero-trust interception, policy enforcement, fuzzing, auditing, external stdio proxying, and visual observability for MCP tool interactions.
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools have clearly distinct actions: lookup server facts, compare candidate tools/agents, view node stats, and record an interaction. Although interaction data appears in both get_lowdown and compare_tools, their outputs and purposes are distinct enough to avoid confusion.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern: get_lowdown, compare_tools, get_node_stats, record_interaction. The convention is predictable throughout.

    Tool Count5/5

    Four tools is a well-scoped set for a reputation/proxy server: one lookup tool, one comparison tool, one contribution recorder, and one node-status tool. Each has a clear role and there is no unnecessary bloat.

    Completeness4/5

    The surface covers the core lifecycle of looking up a server, comparing candidates, contributing interaction data, and checking node contribution. Minor gaps exist, such as no search/list operation and no dedicated single-agent profile beyond compare_tools, but agents can work around them.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data