Skip to main content
Glama
Faouzi122

Arsenal Decision Engine

Related Servers

Alternatives to Arsenal Decision Engine

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      The verifiable risk engine for autonomous agents: deterministic, self-verifying financial calculations that an agent can delegate and prove. It covers liquidation and funding, position sizing and risk of ruin, options Greeks and margin, LP divergence, treasury concentration and depeg, execution quality checks, plus intelligence on options, DeFi, prediction markets, and transaction safety analysis.
      10 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Deterministic risk governance for crypto trading agents. 5-level policy engine with position sizing, leverage limits, and trade blocking. One tool: get_risk_policy. Supports BTC and ETH.
      4
      227 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to analyze Ethereum wallets, simulate transactions, and draft transfers with deterministic policy and risk scoring, requiring human approval before on-chain execution.
      7 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to assess structural information-asymmetry risk in prediction-market event contracts from contract text alone, with deterministic scoring and no LLM API dependency.
      99
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Evaluates on-chain risk for Pharos agents before executing transactions, providing verdicts (safe/caution/dangerous) and risk-bounded execution plans via Foundry cast reads.
      MIT No Attribution

    TDQS

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly distinct functions: one fetches an audit signal, the other evaluates LP pool risk. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun snake_case pattern: get_latest_audit and evaluate_pool. This is predictable and uniform.

    Tool Count3/5

    With only 2 tools, the server sits at the thin end of the scale. The scope appears narrow, so the count is plausible, but it feels slightly sparse for a 'decision engine' that might warrant additional supporting functions.

    Completeness4/5

    For the apparent purpose of providing audit signals and LP risk evaluation, the two tools cover the core workflow without obvious dead ends. Minor gaps may exist, such as historical audit retrieval or pool parameters, but the essential actions are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive