Ceki
Related Servers
Alternatives to Ceki
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceOpen protocol for AI-agent coordination of professional services. Scheduling, identity, delivery verification, and financial settlement across any vertical.10107 npm1Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to request vetted human assistance over MCP, including estimating, posting, polling, canceling, listing tasks, and uploading files for answers.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create profiles, search and apply for jobs, post jobs and threads, and build verifiable records of delivered work through a remote Streamable HTTP MCP endpoint.MIT
- AlicenseAqualityBmaintenanceYour AI finds the right people for you. Agent-to-agent networking via MCP. Publish what you need, match against other agents, both humans approve before connecting. Ed25519 signed, hosted API.7165 npm7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceUniversal coordination hub for AI agents. Find collaborators, negotiate terms, form contracts, and build reputation through an MCP interface. Supports natural language search across agent networks.5MIT
- AlicenseAqualityCmaintenanceMCP server exposing the Swarmwage agent hire protocol as tools for any MCP-compatible AI agent (Claude Desktop, Claude Code, Cursor, Cline, etc.)113MIT
TDQS
Scored across 24 tools
Most tool groups (auth, wallet, browser, specialists) have clearly distinct actions, and descriptions clarify resource/action pairs. However, get-schedules and get-my-bookings both list the user's bookings/sessions and could easily be confused.
Nearly all tools follow a lowercase hyphenated action-object pattern with clear verbs like get, create, request, and post. The browser-* tools reverse this to object-action (browser-navigate, browser-click), but the pattern is readable and internally consistent within that cluster.
24 tools is at the high end for an MCP server, though the broad platform scope (auth, specialists, wallet, browser automation, jobs) provides some justification. It still feels heavier than a typical well-scoped tool set and could benefit from consolidation or a narrower focus.
Core workflows exist for registration, specialist discovery, wallet funding, and browser automation, but several lifecycles are incomplete: jobs can be created/listed but not deleted, bookings cannot be cancelled, there is no wallet balance query, and browser automation lacks text/DOM extraction. These gaps are notable but may be workable around for simple agent workflows.