Skip to main content
Glama
honeytones

idios

by honeytones
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to idios

No user-submitted related servers found.

    Related Servers

    • agent-trust

      eamwhite1
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely execute peer-to-peer tasks on the XRP Ledger by locking payment in escrow, submitting proof of completion, and receiving an objective PASS/FAIL judgement from an independent AI referee.
      MIT

    • AI Work Market (AWM)

      darioandyoshi-tech
      F
      license
      Not graded
      quality
      B
      maintenance
      Settlement rails for AI labor — USDC escrow on Base Mainnet, 1% protocol fee, designed for autonomous agents. 10 MCP tools covering the full escrow lifecycle: * Quoting calldata for create-intent, submit-proof, release-funds (broadcast gated) * Single-call x402 payment binding (replaces the 5-step x402 dance with one HMAC-signed POST) * Server-side reputation from on-chain event scan * Li
      -

    • arbitova-mcp-server

      jiayuanliang0716-max
      A
      license
      A
      quality
      D
      maintenance
      Non-custodial on-chain escrow + AI arbitration for agent-to-agent USDC payments on Base. Seven tools wrap a verified EscrowV1 contract — create, deliver, confirm, dispute, resolve — with read-only introspection if no wallet key is provided.
      7
      2
      MIT

    • Agent Guild

      AgentTanuki
      A
      license
      B
      quality
      B
      maintenance
      Agent trust checks, reputation and signed passports. Glama's build is a separate local Guild with an empty graph and its own issuer. Registrations and evidence stay local. Use the remote MCP connector for the shared hosted Guild; its free preflight and metered trust services are separate.
      43
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 26 tools

    Disambiguation4/5

    Each tool maps to a distinct contract lifecycle action or query, and the descriptions are highly specific, making misselection unlikely. A few pairs share similar name prefixes (claim_funds vs claim_after_timeout, the void_* tools) but their conditions and roles are clearly delineated.

    Naming Consistency2/5

    The tool names mix verb_noun (create_contract_b, view_contract, claim_funds) with noun_verb (worker_register, worker_deregister, worker_reclaim, treasury_sweep) and a few irregulars (mutual_cancel, claim_after_timeout, void_claim_requester). This inconsistency makes it harder to predict tool names.

    Tool Count3/5

    26 tools is on the heavy side, somewhat above the typical 3-15 range, but the broad scope (contract lifecycle, dispute resolution, worker bonds, marketplace discovery) justifies most of them. It feels slightly over-scoped but still manageable.

    Completeness4/5

    The tool surface covers the full escrow lifecycle: create, commit, deliver, approve, dispute, claim, refund, void, plus worker bond registration/reclaim and marketplace discovery. Minor gaps include no way to list a user's contracts or cancel an Open contract before expiry, but these can be worked around by tracking job IDs or waiting for expiry.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources