Skip to main content
Glama
Sign In
crewpay

crewpay

by fxams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to crewpay

No user-submitted related servers found.

    Related Servers

    • @txn-dev/mcp-server

      polyxmedia
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants such as Claude, Cursor, and Windsurf to create and fund agent wallets, check balances, and move money idempotently between wallets. It also lets them find and hire people by skill, rate, and rating through posted jobs with escrowed budgets, deliverables, payment release, and disputes.
      13
      50 npm
      MIT

    • groundcrew

      AnthonyDavidAdams
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables many agents to coordinate on a single public problem through MCP tools for reading a crew contract, claiming tasks, submitting source-verified findings, and human review.
      1 npm
      3
      MIT

    • Job Card

      zovo-one
      A
      license
      A
      quality
      A
      maintenance
      Enables trades and field service work to be tracked per job: logging labor hours at worker rates and materials used, keeping running totals in integer cents per currency, and moving each job through a status machine from open to invoiced or archived. It also produces daily or weekly summaries of hours and value, and renders a printable card with a signature line for client sign-off.
      11
      0
      MIT

    • AgentTrust

      eamwhite1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for agent-to-agent payments on the XRP Ledger — job marketplace, crypto-condition escrow, AI-verified work delivery, trust scoring, and wallet bootstrap from Coinbase.
      2
      44
      1
      MIT
    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

    A3.7/5.0

    Scored across 16 tools

    Disambiguation3/5

    Several tools overlap in the launch pipeline: crew_launch, crew_launch_dry_run, crew_build_unsigned, crew_submit_signed, and crew_wire_fees all touch coin creation/fee wiring, and crew_search_kols vs crew_list_kols are closely related directory tools. Descriptions do clarify the distinctions (search by handle/wallet, list to browse, dry-run vs mainnet), but an agent can easily misselect at the launch/fee step.

    Naming Consistency4/5

    Every tool uses the crew_ prefix with snake_case verb_noun structure (crew_list_kols, crew_claim_key, crew_notify_hired_crew). Minor deviation with adjective-style names like crew_submit_signed and crew_build_unsigned, but overall cohesive and predictable.

    Tool Count4/5

    16 tools is slightly heavy but each covers a distinct phase of the launch lifecycle (key claim, discovery, KOL selection, build/sign/submit, dry-run, wire, lock, crank, proof). It sits at the top of a comfortable range without obvious filler.

    Completeness4/5

    The surface covers the full launch flow: key acquisition, KOL discovery/autohire, notification, dry-run, mainnet launch, fee wiring, holder locking, fee distribution (crank), status checks, and proof. Core workflows are covered; gaps like editing/canceling an in-flight launch or explicit crew roster management are minor.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources