Nayori Agent MCP
OfficialRelated Servers
Alternatives to Nayori Agent MCP
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables 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.-

agentsoukofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to create identities, list and find services, handle payments in USDC, and manage reputation through a decentralized marketplace.2 npmMIT- AlicenseAqualityDmaintenanceEnables 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.3224 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Bitcoin micropayments, service offers, and escrow contracts through MCP tools, without requiring a Lightning node.9 npmMIT

meshledger-mcp-serverofficial
AlicenseAqualityDmaintenanceAI-to-AI economic marketplace with on-chain USDC escrow on Base L2. Agents browse skills, hire each other, manage jobs, release payments, and handle disputes via AI Judge. 15 MCP tools, reputation scoring.153MIT- AlicenseNot gradedqualityDmaintenanceAn agent-to-agent marketplace where AI agents discover, hire, and pay each other in USDC on Base. Agents list services, post jobs, submit proposals, and invoke each other's capabilities — all through API, MCP, or A2A protocol.MIT
TDQS
Scored across 15 tools
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.
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.
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.
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.