Skip to main content
Glama
Agent Decoy Gateway

Agent Decoy Gateway

Related Servers

Alternatives to Agent Decoy Gateway

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables transparent MCP proxying with a hash-chained effect ledger, classifying agent actions by reversibility, enforcing approval gates, and dry-run previews of sessions.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP agents such as Claude and Cursor to start runs on a live Robinhood Chain fork, read balances and quotes, request swaps under policy checks, and review verdicts and traces without holding a key.
      8
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Free seven-tool proof loop for MCP agents: scoped sessions, bounded authorization, typed outcomes, evidence-bound claims, and tamper-evident local closure. Upgrade to Complete Local for durable memory, recovery, signed traces, release verification, and multi-agent workflows.
      7
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      MCP bridge that lets any MCP client drive the Alethia runtime for agent-native E2E testing. It provides a per-step policy gate that blocks destructive actions with a cryptographic audit trail.
      15
      22 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to propose policy-gated treasury payments and swaps, check pending human approvals, read transaction receipts, and locally verify their integrity through MCP tools.
      MIT

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: one opens/creates a synthetic settlement-reference trail, while the other follows an existing reference handle. The descriptions make the sequence and action boundaries explicit, so an agent should not confuse them.

    Naming Consistency5/5

    Both names follow a consistent verb_noun pattern: lookup_settlement_reference and follow_settlement_reference. The shared object name reinforces the relationship without creating naming ambiguity.

    Tool Count3/5

    Two tools is thin for a gateway surface, even if the intended workflow is deliberately minimal. The set is not bloated, but it sits at the borderline where more lifecycle operations may be expected.

    Completeness3/5

    The basic open-and-follow workflow is covered, but there is no visible way to list trails, inspect status, close/reset a trail, or handle errors beyond the hard step limit. These are notable gaps for a stateful reference-trail domain, though agents may work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues