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.
      15 npm
      10
      MIT
    • A
      license
      A
      quality
      C
      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
    • F
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
      46
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides an MCP stdio interface for AI agents to propose tool calls that are validated against task policy, held for human approval when required, executed in a sandboxed Linux environment, and recorded in an audit log.
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a mostly distinct purpose: single-entity lookup, interaction recording, multi-entity comparison, and node stats. get_lowdown and compare_tools both surface reputation data, but one targets a specific entity while the other ranks multiple entities, so confusion is limited.

    Naming Consistency5/5

    All tools use consistent snake_case with a verb-first pattern: get_lowdown, record_interaction, compare_tools, and get_node_stats. The convention is predictable and readable throughout.

    Tool Count5/5

    Four tools is well-scoped for a reputation proxy focused on checking, recording, comparing, and node-level statistics. Each tool earns its place without redundancy.

    Completeness4/5

    The core lifecycle is covered: check reputation before use, record after use, compare providers, and inspect node contribution. Minor gaps exist around listing/discovering entities or managing recorded data, but the primary workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues