Flagbearer
REMOTE · MCP.FLAGBEARER.DEV
Feature flags for coding agents: create flags, roll them out gradually and write the flag code.
Available components
Last scanned (20 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1363 tokens (~123/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (82% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1127 → 1363 ▼ functional
- New tool “create_application” functional
- New tool “create_client_key” functional
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 74
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 21 Nov 2026 · Probed https://mcp.flagbearer.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.flagbearer.dev | CN=YE1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6da9cb2706fd7127923fc52f911bb21aac4 |
| SANs: mcp.flagbearer.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.flagbearer.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| flagbearer.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.flagbearer.dev/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.flagbearer.dev/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.flagbearer.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.flagbearer.dev |
| Authorisation server | https://flagbearer.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.flagbearer.dev | Verified | 200 | |
| http (plaintext) | http://mcp.flagbearer.dev | HTTPS enforced | 308 | https://mcp.flagbearer.dev/ |
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 →
check_sdk_setup Check SDK setup ~85
What looks wrong with how an application's SDKs are set up, per environment, from what they sent in the last day: flags the code checks that don't exist, wrong or leaked keys, old SDK versions, and environments nothing has connected to. Call this when flags aren't behaving as expected, and after adding flag code and running the app.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
No output schema declared.
No examples provided.
create_application Create an application ~89
Create an application in an organization, usually one per product or codebase, like Storefront. It comes with development, staging and production environments. Ask the user for the name if it isn't obvious from the project. Then create flags in it with create_flag, and a client key with create_client_key for browser and mobile code.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| organizationId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| application | object | yes | – |
| environments | array | yes | – |
No examples provided.
create_client_key Create a client key ~93
Create a public client key for one environment, for browser and mobile SDKs (react, react-native, ios, android, browser). It's safe in app code. Each environment needs its own. Server SDKs need a secret server key instead, which only an admin can create in the Flagbearer dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| environment | string | yes | – |
| name | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| clientKey | string | yes | – |
| environment | string | yes | – |
No examples provided.
create_flag Create a flag ~70
Create a feature flag in an application. It starts off in every environment; use set_flag to turn it on. The key is what code checks, like new-checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| description | – | yes | – |
| key | string | yes | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| flag | object | yes | – |
No examples provided.
generate_flag_types Generate typed flag keys ~124
The text of a TypeScript file listing an application's flag keys, so a misspelled key is a type error and editors autocomplete keys. Write the returned text to the path exactly as it is, and commit it. Only for TypeScript projects using @flagbearer/web (React and browser apps), @flagbearer/node or @flagbearer/react-native. Call it when setting up flags in such a project, and again after creating a flag.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| out | string | – | – |
| sdks | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contents | string | yes | – |
| flags | array | yes | – |
| path | string | yes | – |
No examples provided.
get_sdk_docs Get SDK docs ~97
The current Flagbearer SDK docs for a platform (react, react-native, ios, android, browser, node, python, go, java, dotnet, ruby, rust, cpp or php), plus one environment's SDK address and public client key. Call this before writing code that checks a flag, and follow it.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| environment | string | yes | – |
| platform | string | yes | – |
No output schema declared.
No examples provided.
get_user_flags Get a user's flags ~152
What a user should have got for every flag in one environment, by email or user key, with the reason (off, tester or rollout and their bucket), what their SDK reported that UTC day (seen), and any changes that day that flipped their result. Use it when a bug report says a feature stopped working, or works for some users and not others. times is a list of ISO timestamps to show side by side, like before and after a report; leave it out for now. An email the SDK saw with several user keys gives one entry per key.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| environment | string | yes | – |
| times | array | – | – |
| user | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
list_applications List applications ~30
List the applications in an organization. Flags belong to an application.
| Name | Type | Req | Description |
|---|---|---|---|
| organizationId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| applications | array | yes | – |
No examples provided.
list_flags List flags ~36
List an application's feature flags with whether each is on, and its rollout percent, in every environment.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| environments | array | yes | – |
| flags | array | yes | – |
No examples provided.
list_organizations List organizations ~64
List the Flagbearer organizations you belong to. Start here to find an organization's ID. This connection only covers the organizations listed. If the project's application isn't in any of them, tell the user before writing flag code, and ask them to reconnect and approve the right organization.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| organizations | array | yes | – |
No examples provided.
set_flag Turn a flag on or off ~143
Turn a flag on or off in one environment, by flag key and environment key. When turning a flag on, rolloutPercent says who gets it: 100 for everyone, or a percentage of users. Ask the user whether it should be on for everyone. Without rolloutPercent it's 0, which turns it on only for the environment's testers. Changing production needs confirmProduction: true. Only send that after the user has confirmed the change.
| Name | Type | Req | Description |
|---|---|---|---|
| applicationId | string | yes | – |
| confirmProduction | boolean | – | – |
| enabled | boolean | yes | – |
| environment | string | yes | – |
| flagKey | string | yes | – |
| rolloutPercent | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | yes | – |
| environment | string | yes | – |
| flagKey | string | yes | – |
| rolloutPercent | number | yes | – |
No examples provided.
How do I install the Flagbearer MCP server?
Flagbearer is a hosted endpoint at https://mcp.flagbearer.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.flagbearer.dev
claude mcp add --transport http dev-flagbearer-flagbearer 'https://mcp.flagbearer.dev/'
What is the Flagbearer MCP server?
Flagbearer is an MCP server listed in the public MCP registry as dev.flagbearer/flagbearer. Feature flags for coding agents: create flags, roll them out gradually and write the flag code. This page covers its hosted endpoint (https://mcp.flagbearer.dev).
Is the Flagbearer MCP server safe to use?
Flagbearer scores 78 out of 100 on VerifyMCP. 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 Flagbearer MCP server expose?
Flagbearer exposes 11 tools: list_organizations, list_applications, create_application, list_flags, create_flag, and 6 more. Their descriptions and schemas cost roughly 983 tokens of context every time the server is loaded.
Does the Flagbearer MCP server require authentication?
Yes. Flagbearer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Flagbearer MCP server still maintained?
Flagbearer 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 Flagbearer MCP server?
VerifyMCP ran 13 checks on Flagbearer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.