Featureflip
NPM · @FEATUREFLIP/MCP · SCANNED SEP 20
Manage Featureflip feature flags, targeting and rollouts from AI agents and editors.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1558 tokens (~82/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 39% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Featureflip MCP server?
Featureflip runs locally as an npm package, launched with npx -y @featureflip/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @featureflip/mcp
claude mcp add canopy-labs-featureflip -- npx -y @featureflip/mcp
{
"mcpServers": {
"canopy-labs-featureflip": {
"command": "npx",
"args": [
"-y",
"@featureflip/mcp"
]
}
}
} {
"servers": {
"canopy-labs-featureflip": {
"command": "npx",
"args": [
"-y",
"@featureflip/mcp"
]
}
}
} codex mcp add canopy-labs-featureflip -- npx -y @featureflip/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"canopy-labs-featureflip": {
"type": "local",
"command": [
"npx",
"-y",
"@featureflip/mcp"
],
"enabled": true
}
}
} openclaw mcp add canopy-labs-featureflip --command npx --arg -y --arg @featureflip/mcp
mcp_servers:
canopy-labs-featureflip:
command: "npx"
args: ["-y", "@featureflip/mcp"] {
"McpServers": {
"canopy-labs-featureflip": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@featureflip/mcp"
]
}
}
} assistant mcp add canopy-labs-featureflip -t stdio -c npx -a -y @featureflip/mcp
{
"mcpServers": {
"canopy-labs-featureflip": {
"command": "npx",
"args": [
"-y",
"@featureflip/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
- Security disclosure: fail → pass ▲ functional
- 18 Sept 26 +1
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.6 → 0.1.7 functional
- 17 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 16 Sept 26 +4
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: 1.00 → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 38 functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.1.4 → 0.1.6 functional
- Package version: 0.1.4 → 0.1.5 functional
- 29 Aug 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@featureflip/mcp@0.1.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
archive_flag Archive feature flag ~135
Archive a flag (soft-hide, evaluation stops serving it). Reversible with restore_flag. Refused with FLAG_RECENTLY_EVALUATED while live traffic is still evaluating the flag, because archiving makes every caller fall back to its own hardcoded default — normally that means the code removal has merged but not deployed yet, and the refusal clears itself once it has.
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | yes | – |
| force | boolean | – | Archive even though traffic is still evaluating the flag. Only for clients that can never be updated (old mobile app versions), where traffic will never drain on its own. |
| project | string | yes | – |
No output schema declared.
No examples provided.
create_flag Create feature flag ~155
Create a feature flag. type is one of Boolean|String|Number|Json. Boolean flags get true/false variations automatically; for other types pass initialVariations. The flag is created in every environment of the project (disabled).
| Name | Type | Req | Description |
|---|---|---|---|
| clientSideVisible | boolean | – | Expose to client-side SDKs (browser/mobile) |
| description | string | – | – |
| idempotency_key | string | – | Idempotency-Key header for safe retries |
| initialVariations | array | – | – |
| key | string | yes | Unique flag key, e.g. checkout-v2 |
| name | string | yes | – |
| project | string | yes | Project key |
| tags | array | – | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
delete_flag Delete feature flag ~65
PERMANENTLY delete a flag across all environments. Fails with FLAG_HAS_DEPENDENTS if other flags use it as a prerequisite. Prefer archive_flag unless the flag must be fully removed.
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | yes | Flag key or id |
| project | string | yes | – |
No output schema declared.
No examples provided.
find_stale_flags Find stale flags ~90
Find flags that look ready for code cleanup: not updated in N days AND either enabled in every environment (verify rollout is complete before removing — per-rule percentage ramps are not inspected) or disabled in every environment (dead — remove flag and code path). Checks at most 50 candidates per call.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Minimum age in days since last update |
| project | string | yes | – |
No output schema declared.
No examples provided.
flag_status Flag status across environments ~44
Compact cross-environment view of one flag: enabled state, strategy, default variation, and prerequisites per environment.
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | yes | – |
| project | string | yes | – |
No output schema declared.
No examples provided.
get_flag Get feature flag ~45
Get one feature flag with its variations and metadata. Address by flag key or id.
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | yes | Flag key or id |
| project | string | yes | Project key |
No output schema declared.
No examples provided.
get_segment Get user segment ~46
Get one user segment (its conditions, id, and metadata) by key or id.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project key |
| segment | string | yes | Segment key or id |
No output schema declared.
No examples provided.
get_targeting Get targeting rules ~48
Get a flag's current targeting configuration (enabled flag + ordered rules) in one environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | – |
| flag | string | yes | – |
| project | string | yes | – |
No output schema declared.
No examples provided.
list_environments List environments ~48
List the environments of a project (e.g. development, staging, production).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| project | string | yes | Project key |
No output schema declared.
No examples provided.
list_flags List feature flags ~94
List feature flags in a project. Filter with search (key/name substring), tag, type, archived. Paginated via cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = only archived, false = only active |
| cursor | string | – | – |
| limit | integer | – | – |
| project | string | yes | Project key |
| search | string | – | – |
| tag | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
list_projects List projects ~53
List projects in the Featureflip organization. Paginated: pass cursor from next_cursor to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from a previous response |
| limit | integer | – | Page size (default 20) |
No output schema declared.
No examples provided.
list_segments List user segments ~51
List reusable user segments in a project. Segments are referenced from targeting rules via userSegmentId.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| project | string | yes | Project key |
No output schema declared.
No examples provided.
manage_variation Add, update, or remove a variation ~133
Manage a flag's variations. action=add requires key + value; action=update/remove require variationId (get ids via get_flag). Removing a variation fails with VARIATION_HAS_DEPENDENTS if other flags depend on it.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| description | string | – | – |
| flag | string | yes | – |
| key | string | – | Required for add; immutable afterwards |
| name | string | – | – |
| project | string | yes | – |
| value | string | – | Variation value serialized as a string; required for add |
| variationId | string | – | Required for update/remove |
No output schema declared.
No examples provided.
restore_flag Restore archived flag ~28
Restore a previously archived flag.
| Name | Type | Req | Description |
|---|---|---|---|
| flag | string | yes | – |
| project | string | yes | – |
No output schema declared.
No examples provided.
toggle_flag Toggle flag in environment ~67
Enable or disable a flag in ONE environment. Affects live evaluation immediately — double-check the environment.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| environment | string | yes | Environment key, e.g. production |
| flag | string | yes | Flag key or id |
| project | string | yes | – |
No output schema declared.
No examples provided.
update_flag Update feature flag metadata ~84
Update flag name/description/tags/clientSideVisible. Key and type are immutable. Use toggle_flag / update_targeting for behavior changes.
| Name | Type | Req | Description |
|---|---|---|---|
| clientSideVisible | boolean | – | – |
| description | string | – | – |
| flag | string | yes | Flag key or id |
| name | string | – | – |
| project | string | yes | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
update_flag_environment_config Update flag environment config ~160
Update a flag's per-environment serving config: defaultVariationId (served on fallthrough, required), strategy (SingleVariation | PercentageRollout | TargetedRollout — only SingleVariation is currently supported at the environment level), and prerequisites. Percentage rollouts are configured on targeting rules via update_targeting.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultVariationId | string | yes | Variation id to serve on fallthrough — required by the API |
| environment | string | yes | – |
| flag | string | yes | – |
| prerequisites | array | – | Flags that must evaluate to the expected variation before this flag serves. Omit to leave existing prerequisites untouched; pass a list (possibly empty) to replace them wholesale. |
| project | string | yes | – |
| strategy | string | – | – |
No output schema declared.
No examples provided.
update_targeting Replace targeting rules ~74
REPLACE all targeting rules of a flag in one environment (full PUT — rules not included are removed). Rules are evaluated in order. Get the current rules first with get_targeting.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | – |
| flag | string | yes | – |
| project | string | yes | – |
| rules | array | yes | – |
No output schema declared.
No examples provided.
wrap_feature Wrap a feature in a new flag ~138
Create a Boolean feature flag and get back the SDK code snippet to guard the new code path with it. Returns the snippet only — apply the edit yourself. The flag starts DISABLED in every environment; enable it with toggle_flag when ready.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What this flag guards |
| idempotency_key | string | – | – |
| key | string | yes | Flag key, e.g. new-checkout |
| language | string | yes | SDK language of the codebase being edited |
| name | string | – | Display name; defaults to the key |
| project | string | yes | Project key |
| tags | array | – | – |
No output schema declared.
No examples provided.
What is the Featureflip MCP server?
Featureflip is an MCP server listed in the public MCP registry as io.github.canopy-labs/featureflip. Manage Featureflip feature flags, targeting and rollouts from AI agents and editors. This page covers its npm package (@featureflip/mcp).
Is the Featureflip MCP server safe to use?
Featureflip scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Featureflip MCP server expose?
Featureflip exposes 19 tools: list_projects, list_environments, list_segments, get_segment, list_flags, and 14 more. Their descriptions and schemas cost roughly 1,558 tokens of context every time the server is loaded.
Is the Featureflip MCP server still maintained?
Featureflip is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Featureflip MCP server under?
Featureflip declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.