Skip to main content
Glama
0xR-1

clawton-agentos

by 0xR-1

Related Servers

Alternatives to clawton-agentos

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to trade on Binance through a governed MCP proxy that enforces configurable policies, requires a recorded rationale before orders, detects prompt injection, logs all actions in a tamper-evident audit trail, and blocks execution until a human approves.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to evaluate every payment intent against user-signed, on-chain-anchored policies before money moves, returning allow, deny, or human-approval verdicts. Provides policy versioning, revocation, spend reports, and audit trails through MCP tools that agents cannot alter without the owner's key.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to propose wallet payments while a local, human-authored policy decides whether each transaction is approved, requires human confirmation, or is refused, and records every decision in a signed, append-only ledger.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and manage contract-guarded USDC wallets on Base with enforceable per-payment, daily, and monthly caps, vendor allowlists, escalation thresholds, and freeze controls. It provides read-only policy checks plus unsigned transaction proposals for payments, funding, vendor management, wallet creation, and module deployment without holding keys or broadcasting.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pay x402 endpoints on Cardano through a policy-gated wallet with spend caps, payee allowlists, human approval, and an audit log.
      65 npm
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are cleanly separated by intent type: one evaluates x402 payments and the other evaluates Binance trades. Their names and descriptions make the correct choice obvious, with no functional overlap despite both being pre-flight checks.

    Naming Consistency5/5

    Both tools follow the same check_<intent> convention: check_payment_intent and check_trade_intent. The pattern is predictable and makes the set easy to navigate.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 range, but the server appears intentionally scoped to guardrail checks for two specific intent types. Each tool earns its place and there is no redundant surface.

    Completeness4/5

    For the stated purpose of payment and trade safety checks, the server covers both target intents. It lacks any cap-management or status tools, but those may be intentionally external and agents can proceed with the checks provided.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues