Verfy

MCP servers / @launchdarkly/mcp-server

MCP tool changes

@launchdarkly/mcp-server

2 of its last 5 updates changed what the agent reads: 0 tool descriptions rewritten, up to 0.7.2.

npm package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. npm page · Method and limits · this data as JSON.

Release by release

0.7.1 → 0.7.2

patch release, 27 October 2026

Added: create-experiment, create-experiment-iteration, create-metric, get-experiment, get-metric, list-experiments, list-experiments-any-environment, list-metrics, update-experiment, update-metric

create-ai-config: input schema changed

create-ai-config-variation: input schema changed

create-feature-flag: input schema changed

get-audit-log-entries: input schema changed

update-ai-config: input schema changed

update-ai-config-variation: input schema changed

0.7.0 → 0.7.1

patch release, 22 October 2026

No tool definition changed.

0.6.2 → 0.7.0

minor release, 5 October 2026

No tool definition changed.

0.6.1 → 0.6.2

patch release, 8 May 2026

Added: get-audit-log-entries

0.6.0 → 0.6.1

patch release, 20 March 2026

No tool definition changed.

Releases tried: 0.6.0 (2026-03-02); 0.6.1 (2026-03-20); 0.6.2 (2026-05-08); 0.7.0 (2026-10-05); 0.7.1 (2026-10-22); 0.7.2 (2026-10-27).

Tools in 0.7.2

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 0.7.2
ToolDescriptionPin
get-audit-log-entriesFetches audit log entries for a LaunchDarkly account. Use the `spec` parameter with format `proj/<projectKey>:env/<envKey>:flag/<flagKey>` to query a specific flag's change history (use `env/*` for all environments). The `before` and `after` parameters accept Unix epoch timestamps in milliseconds for date-range filtering. Returns at most 20 entries per call, ordered newest-first. e7ef0ba70400
get-code-referencesIdentifies which repositories have code references to a given flag, helping agents determine if they're operating on the correct repository and understand the scope of cleanup (single vs multi-repo). 71a290fc44c5
get-flag-status-across-environmentsReturns lifecycle status (new, active, inactive, launched) based on actual usage patterns, evaluation counts, and configuration stability. This is the key intelligence for removal readiness assessment. 2b54626c0eda
list-feature-flagsRetrieves all feature flags within a project, including metadata and targeting rules. Enables AI agents to enumerate existing flags for inspection, configuration analysis, or generating flag usage reports across environments. acb8dd3c9c29
create-feature-flagCreates a new feature flag within a project. AI agents can use this operation to define feature toggles for controlled rollouts, experimentation, or gated features, automating the flag setup process. c24a23f2a396
get-feature-flagFetches the full configuration for a specific feature flag, including environments, variations, and targeting rules. Useful for agents auditing or managing specific feature toggles in a detailed, contextual manner. 672ed6f52415
update-feature-flagUpdates the configuration of an existing feature flag. Enables agents to change targeting rules, modify variations, or adapt rollout strategies dynamically in response to user behavior or experiment results. 436c9b4a63db
delete-feature-flagRemoves a feature flag from the project. Used by AI agents to clean up deprecated toggles that are no longer in use, improving system hygiene and maintainability. 77f52cff0cdb
list-metricsLists metrics in a project. Use to find metric keys to attach to an experiment.ac97b561de5d
create-metricCreates a metric in a project, for use in experiments and guarded rollouts.048cd787914f
get-metricFetches one metric's configuration.d2be9e27f38d
update-metricUpdates a metric using a JSON patch.fb68cc6c24fd
get-environmentsIdentifies which environments exist in a project and determines which are marked as "critical" (production, staging, etc.). Allows agents to programmatically identify critical environments instead of hardcoding assumptions. c85d1bc6f1ab
list-experimentsLists experiments in a project environment, including their current iteration and status.3682940bc14a
create-experimentCreates an experiment in a project environment, with an initial iteration that sets the hypothesis, flag, treatments, and metrics.28db54b2c456
get-experimentFetches one experiment, including its current and past iterations, treatments, and metrics.1658e7730845
update-experimentUpdates an experiment using semantic patch instructions, such as starting or stopping an iteration, or changing its name or description.5191075c34b0
create-experiment-iterationCreates a new iteration of an experiment. Start it afterwards with update-experiment.1aa8902ee6a7
list-experiments-any-environmentLists experiments in a project across all environments. Use to discover experiments before fetching one by environment.97aa6b911bb4
get-ai-config-targetingRetrieves the targeting details of a specific AI Config, including individual targets, rules, and rollouts.db484ae90904
update-ai-config-targetingUpdates the targeting of an existing AI Config.e299d202c632
list-ai-configsRetrieves AI configuration settings for a specific project. This endpoint allows agents to access and modify AI-related configurations, ensuring that the AI's behavior aligns with project requirements and user expectations. 1a6ea0960a6b
create-ai-configCreates a new AI Config within a project. Useful for setting up LLM configurations programmatically. f8dd29276c54
delete-ai-configDeletes an AI Config and its associated variations. Intended for cleanup or deprecation workflows. 885d308998c6
get-ai-configRetrieves details of a specific AI Config, including variations and model settings.55f1ea5fe8e9
update-ai-configUpdates metadata or configuration of an existing AI Config.9cc2a33cfa2f
create-ai-config-variationAdds a new variation to an AI Config, supporting experimentation or multi-model strategies. e2c95dae1886
delete-ai-config-variationDeletes an AI Config variation.4ef02e9e61a6
get-ai-config-variationRetrieves an AI configuration variation.abeb61a5a8f8
update-ai-config-variationUpdates a specific variation within an AI Config. Enables fine-tuned control of model behavior. 8e69186c77ed

Lock these tools

Pin what @launchdarkly/mcp-server serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.