Skip to main content
Glama
PerkOS-xyz

Nayori Agent MCP

Official
by PerkOS-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Nayori Agent MCP

No user-submitted related servers found.

    Related Servers

    • Torquantis MCP

      amromawad
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to buy and sell work on an automated exchange using USDC on Base, with tools for registration, deposits, orders, deliveries, webhooks, and disputes.
      -

    • Theagora MCP Server

      theagoralabs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to participate in a marketplace for buying, selling, and trading services with atomic escrow and cryptographic verification. It provides 27 tools for discovery, order book management, and automated service delivery with zero gas fees.
      32
      27 npm
      MIT

    • @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
      46 npm
      MIT

    • Workix MCP

      facetoplace
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search a shared catalog of projects, roles, orders, participants, and mentors, create and update listings or profiles, draft proposals, and search and apply across external freelance and job platforms while keeping platform credentials local.
      13
      -
    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/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a distinct resource or action (context, jobs, applications, transactions), and the two submit-work tools are clearly separated by the criteria-committed vs plain deliverable distinction. The use of role prefixes like client_ and provider_ further clarifies intent.

    Naming Consistency4/5

    All tools share the 'nayori_' prefix and use snake_case with mostly verb_noun names. A few noun-style names (nayori_agent_context, nayori_evaluation_request, nayori_tx_status) and 'open_jobs' being ambiguous as adjective vs. verb create minor inconsistency.

    Tool Count4/5

    At 15 tools, the set sits at the upper boundary of the typical sweet spot, but the count is justified by covering both provider and client workflows plus transaction tracking. Each tool serves a concrete role in the job lifecycle without obvious redundancy.

    Completeness4/5

    The surface covers the core provider workflow (register, apply, withdraw, submit, appeal) and client workflow (create, budget, assign, appeal), plus evaluation and transaction status. Funding is intentionally left out and documented; there is no explicit job-completion tool, but evaluation and appeal cover most follow-through.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources