Skip to main content
Glama
jiayuanliang0716-max

arbitova-mcp-server

by jiayuanliang0716-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to arbitova-mcp-server

No user-submitted related servers found.

    Related Servers

    • AI Work Market (AWM)

      darioandyoshi-tech
      A
      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
      MIT

    • Mark: agent escrow

      yuvlero
      A
      license
      Not graded
      quality
      B
      maintenance
      Non-custodial 2-of-3 Bitcoin escrow for AI agents. Two agents agree on signed terms, the buyer funds over Lightning, the seller delivers and gets paid over Lightning, and a neutral arbiter key only breaks ties.
      1,028 npm
      MIT

    • idios

      honeytones
      A
      license
      A
      quality
      A
      maintenance
      Private escrow for AI agent work on Beam mainnet an agent locks payment, the worker locks collateral, and delivery settles on hash match or review, with M of N arbitrator voting and slashable worker bonds as the dispute backstop. 22 tools cover the full contract lifecycle, and dispute voting is deliberately not an agent tool, so an agent can never rule in its own favour.
      26
      MIT

    • mercadopleis

      castiquark
      A
      license
      Not graded
      quality
      A
      maintenance
      AI agents hire people for work they can't finish alone (data curation, red-teaming, scraping, transcription), paid via non-custodial USDC escrow on Base. Returns unsigned transactions and holds no keys.
      1
      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.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a unique action in the escrow lifecycle (create, get, mark delivered, confirm, cancel, dispute, escalate). No two tools have overlapping purposes, and descriptions clarify exactly when each should be used.

    Naming Consistency5/5

    All tools follow the pattern 'arbitova_<verb>_<condition>', using snake_case consistently. The names are descriptive and predictable, making it easy to infer the tool's action from its name.

    Tool Count5/5

    7 tools is an ideal size for an escrow management server. Each tool serves a necessary function in the lifecycle without unnecessary redundancy or bloat.

    Completeness5/5

    The tool set covers the full escrow lifecycle: creation, status retrieval, delivery marking, confirmation/cancellation, dispute opening, and escalation. There are no obvious gaps that would hinder an agent from managing an escrow end-to-end.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources