com.devcycle/mcp

MCPcommunitylive
v6.3.2com.devcycleUnknownUpdated 5mo agoGitHub

DevCycle MCP server for feature flag management

DevCycle CLI & MCP Server ========================= This repository contains the DevCycle CLI for managing feature flags from the command line, plus an MCP (Model Context Protocol) server that enables AI coding assistants to interact with DevCycle. Major features include: Fully manage your Features, Variables, Variations and Targeting Rules from the command line Detect and list DevCycle Variable…

Endpoint healthlive
checked 10 days ago · 33ms · 2 endpoints · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http, sse). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
20GitHub stars
6Forks
5mo agoLast update
Package
Authorcom.devcycle
LicenseUnknown
Version6.3.2
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface6 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

keyNo description published

This tool published no description. Forge does not invent one.

diff-patternNo description published

This tool published no description. Forge does not invent one.

featureNo description published

This tool published no description. Forge does not invent one.

userIdNo description published

This tool published no description. Forge does not invent one.

allNo description published

This tool published no description. Forge does not invent one.

environmentNo description published

This tool published no description. Forge does not invent one.

0 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

DevCycle CLI & MCP Server ========================= This repository contains the DevCycle CLI for managing feature flags from the command line, plus an MCP (Model Context Protocol) server that enables AI coding assistants to interact with DevCycle. Major features include: Fully manage your Features, Variables, Variations and Targeting Rules from the command line Detect and list DevCycle Variable usages in your codebase Manage your Self-Targeting Overrides to quickly switch between Variable…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.