zero-trust-feature-team vs noduty planner
zero-trust-feature-team is a plugin bundle for AI coding tools published by bradselph. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). noduty planner is an MCP server published by noduty.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  zero-trust-feature-team | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.23.0 No figure published Not marked · First seen |
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 | zero-trust-feature-team | noduty planner |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (planner.noduty.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 16 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bradselph/zero-trust-feature-team | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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
zero-trust-feature-team
Eight agents and eight slash commands turn a one-line feature request into a tracked implementation pipeline. Independent verification at every gate—no code is written until you approve the plan. State persists across /clear in .claude/feature-state/. Commands: /feature:init, /feature:research, /feature:plan, /feature:review, /feature:implement
noduty planner
Issue tracking for software projects: issues, epics, releases, docs and boards, from your AI.
How to run each
zero-trust-feature-team As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install zero-trust-feature-team@claude-communitynoduty planner As a remote MCP server
claude mcp add --transport http planner https://planner.noduty.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only noduty planner has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: zero-trust-feature-team · What it can do: noduty planner · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.