MCP Task Orchestrator vs Sunaiva Gate — Agent Rule Enforcement
MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Sunaiva Gate — Agent Rule Enforcement is an MCP server published by sunaivacore.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MCP Task Orchestrator |  Sunaiva Gate — Agent Rule Enforcement |
|---|---|---|
| Official MCP Registry | Listed Version: 4.0.2 Forks (GitHub): 25 Stars (GitHub): 214 Not marked · First seen |
Listed Version: 2.0.4 Downloads/month (npm): 268 Downloads/week (npm): 93 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:e2218297471b Forks (GitHub): 25 Stars (GitHub): 214 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | MCP Task Orchestrator | Sunaiva Gate — Agent Rule Enforcement |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 214 | No figure on GitHub |
| Forks (GitHub) (differs) | 25 | No figure on GitHub |
| Last release (differs) | 2026-11-12 | Not published |
| Where it runs (differs) | On your machine (ghcr.io/jpicklyk/task-orchestrator:4.0.2) | Remote server (mcp.sunaivacore.io) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 47, secrets among them: 0 | 3, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jpicklyk/task-orchestrator | Not stated |
| Changes in the last 7 days (differs) | 11 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
MCP Task Orchestrator
Workflow discipline for AI agents: work items, gates, role-scoped tool profiles and runs
Sunaiva Gate — Agent Rule Enforcement
MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution.
How to run each
MCP Task Orchestrator As a local MCP server: Docker image
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:4.0.2Sunaiva Gate — Agent Rule Enforcement As a remote MCP server
claude mcp add --transport http gate https://mcp.sunaivacore.ioRequires: SUNAIVA_GATE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Sunaiva Gate — Agent Rule Enforcement has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Sunaiva Gate — Agent Rule Enforcement publish no list of tools, so we do not compare tools.
Settings each asks for
Only MCP Task Orchestrator asks for
AGENT_CONFIG_DIRAPI_ALLOW_QUERY_TOKEN_FOR_SSEAPI_ALLOW_UNAUTHENTICATEDAPI_AUTH_MODEAPI_ENABLEDAPI_JWKS_ALGORITHMSAPI_JWKS_ALLOW_INSECURE_URLAPI_JWKS_AUDIENCEAPI_JWKS_CACHE_TTL_SECONDSAPI_JWKS_ISSUERAPI_JWKS_MAX_STALE_SECONDSAPI_JWKS_MAX_TOKEN_LIFETIME_SECONDS
Show the remaining 35
API_JWKS_URLAPI_REDACT_NOTE_ATTRIBUTIONAPI_SSE_AUTH_CHECK_INTERVAL_SECONDSAPI_SSE_BUFFER_SIZEAPI_TOKENS_PATHCORS_ALLOWED_HEADERSCORS_ALLOWED_METHODSCORS_ALLOWED_ORIGINSCORS_EXPOSE_HEADERSCORS_MAX_AGE_SECONDSDATABASE_BUSY_TIMEOUT_MSDATABASE_MAX_CONNECTIONSDATABASE_PATHDATABASE_SHOW_SQLDB_COMPACT_ON_UPGRADEFLYWAY_REPAIRFTS_INTEGRITYLOG_FILELOG_LEVELMCP_ALLOWED_HOSTSMCP_ALLOW_UNAUTHENTICATEDMCP_HTTP_HOSTMCP_HTTP_PORTMCP_SERVER_NAMEMCP_SESSION_IDLE_TIMEOUT_MINUTESMCP_TOOL_PROFILEMCP_TRANSPORTREADINESS_FILERESOURCE_LEASES_ENFORCEDRETENTION_AUDIT_EVENTS_DAYSRETENTION_CALL_LOG_DAYSRETENTION_EVENTS_DAYSRETENTION_LEASE_HISTORY_DAYSSCHEMA_MODEUPGRADE_BACKUP
Only Sunaiva Gate — Agent Rule Enforcement asks for
DISABLE_SUNAIVA_GATESUNAIVA_GATE_API_KEY (secret)SUNAIVA_GATE_DRY_RUN
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: MCP Task Orchestrator · What it can do: Sunaiva Gate — Agent Rule Enforcement · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.