dev.openfeature/mcp
NPM · @OPENFEATURE/MCP
MCP server providing OpenFeature SDK installation guides and OFREP flag evaluation
Available components
Last scanned (14 hours ago)
Scores higher than 73% of npm servers
Category Developer Tools
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 Security98
- 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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency58
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to open-feature/mcp). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 192 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 195 tokens (~97/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ofrep_flag_eval" implies "eval" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@openfeature/mcp@0.0.22
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | open-feature/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/open-feature/mcp/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 1520452646 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0c8561a798a573ace1552964d433fa4f0aecb859e992d1c1a28c5791691d4a740b5c4919de1932c6831970622ad7dee987ab633441721bbd5584216e4 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
install_openfeature_sdk ~81
Fetch OpenFeature SDK installation instructions, and follow the instructions to install the OpenFeature SDK. If you are installing a provider, also fetches the provider installation instructions. Also includes documentation and examples for using OpenFeature SDK in your application. Choose the technology that matches the application's language/framework.
| Name | Type | Req | Description |
|---|---|---|---|
| providers | array | – | – |
| technology | string | yes | – |
No output schema declared.
No examples provided.
ofrep_flag_eval ~114
Evaluate feature flags using OpenFeature Remote Evaluation Protocol (OFREP). If flag_key is omitted, performs bulk evaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | object | – | – |
| base_url | string | – | Base URL of your OFREP-compatible flag service. Must be set directly or via environment variables or config file. |
| context | object | – | Context information for flag evaluation |
| etag | string | – | ETag for bulk evaluation |
| flag_key | string | – | If provided, calls single flag evaluation, otherwise performs bulk evaluation. |
No output schema declared.
No examples provided.
How do I install the dev.openfeature/mcp server?
dev.openfeature/mcp runs locally as an npm package, launched with npx -y @openfeature/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 · @openfeature/mcp
claude mcp add dev-openfeature-mcp -- npx -y @openfeature/mcp
What is the dev.openfeature/mcp server?
dev.openfeature/mcp is listed in the public MCP registry as dev.openfeature/mcp. MCP server providing OpenFeature SDK installation guides and OFREP flag evaluation. This page covers its npm package (@openfeature/mcp).
Is the dev.openfeature/mcp server safe to use?
dev.openfeature/mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 dev.openfeature/mcp server expose?
dev.openfeature/mcp exposes 2 tools: install_openfeature_sdk, ofrep_flag_eval. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.
Is the dev.openfeature/mcp server still maintained?
dev.openfeature/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the dev.openfeature/mcp server?
VerifyMCP ran 16 checks on dev.openfeature/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.