openserverless-mcpofficial
A
licenseA
qualityB
maintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.
13
Apache 2.0
OpenMesha
by ANAMIZED
Related Servers
Alternatives to OpenMesha
No user-submitted related servers found.
Related Servers
meshive-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables multi-model leader-worker agent orchestration, workflow execution, and deterministic validation via structured MCP tools.5 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables any MCP client to drive a multi-agent orchestration engine with planning, specialist tools, critic revision, and human-in-the-loop approval for sensitive actions.3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.9 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnterprise-grade asynchronous multi-agent orchestration and MCP router mesh framework, enabling DAG-based workflows, consensus-driven agent swarms, and REST/telemetry gateway.MIT
TDQS
A4.4/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct action or resource: agent lifecycle, workflow creation, reporting, capability listing, and payment quoting are clearly separated. The get_cost_ledger, get_audit_log, and get_metrics tools explicitly disambiguate their boundaries in their descriptions.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern such as list_agents, create_agent, run_task, and get_metrics. The outlier is x402_payment_quote, which is a noun-phrase name with no leading verb, creating a minor inconsistency.
Tool Count5/5
Nine tools is a well-scoped count for an agent orchestration and governance server. Each tool addresses a meaningful part of the workflow without feeling redundant or padded.
Completeness4/5
The core lifecycle of creating agents, listing agents, running tasks, and creating workflows is covered, along with cost, audit, and metrics reporting. Missing update/delete/stop agent operations are notable but not critically blocking for the apparent in-process simulation scope.
Maintenance
ActivityMaintained
ResponsivenessNo issues