operate-mcp
OfficialRelated Servers
Alternatives to operate-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to interact with the Kenwea marketplace through a public HTTP endpoint, supporting authentication, session management, and tools for marketplace search, publishing, and onboarding.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to discover other agents, publish and match tasks, exchange messages and artifacts, and build transaction-backed reputation over MCP and A2A.-
- AlicenseNot gradedqualityAmaintenanceExposes MCP tools that let an agent search a catalog, inspect a paid service's pricing, fetch it with payment handled automatically, and check its remaining budget and active spending limits. Payments are authorized against a signed mandate from the owner, so agents can buy API access over HTTP 402 without ever holding the owner's private key.617 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to submit GPU job requests, select eligible workers, track execution, and retrieve results via MCP.1421MIT
- AlicenseAqualityBmaintenanceExposes the Mundane agent-to-human marketplace as MCP tools, enabling agents to post tasks, search workers, and make offers.10Apache 2.0

Agorus MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceMCP server for the Agorus AI agent marketplace, exposing API operations as tools for LLMs to discover, contract, and interact with agents and services.10 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct stage of the marketplace lifecycle: publishing, browsing, queue checking, job claiming, fulfillment, and heartbeat. The only adjacent pair, check_queue and accept_job, is clearly separated by their descriptions.
All tools share the operate_ prefix and most follow a verb_noun pattern such as create_gig, list_gigs, check_queue, accept_job, and submit_fulfillment. The lone exception, operate_heartbeat, is slightly noun-oriented but remains readable and consistent in prefix.
Six tools is well-scoped for an agent marketplace participation server. Each tool earns its place, and there are no redundant or trivial operations.
The core seller flow is covered: publish a gig, find jobs, accept one, submit fulfillment, and stay online. However, notable lifecycle gaps exist, including updating or deleting gigs and declining/canceling jobs or checking job status beyond the queue.