_ registry / mcp http-sse · checked 12h ago

flagbearer

https://mcp.flagbearer.dev

Registry code: 9b8ad9054d3e6bf0

api record

Flagbearer manages this project's feature flags. When the user asks to put something behind a flag, gate a feature or roll something out gradually, start here, even if the code already has a flag helper to copy. The work isn't done until the flag exists in Flagbearer: a key the code checks but nobody created is always off. Creating a flag is safe: it starts off in every environment, and production only changes through set_flag after the user confirms. If the project's application isn't in any organization list_organizations returns, tell the user before writing flag code. If the organization…

endpoint
https://mcp.flagbearer.dev
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is flagbearer live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is flagbearer free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does flagbearer have?
11 tools: list_organizations, generate_flag_types, check_sdk_setup, create_application, create_flag, list_applications, list_flags, set_flag, ….
Is flagbearer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
514ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
11 auth-required 11 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_organizations auth-required 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • generate_flag_types auth-required 39h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId",
        "sdks"
      ],
      "properties": {
        "out": {
          "type": "string",
          "pattern": "^[^\\r\\n`]{1,200}$"
        },
        "sdks": {
          "type": "array",
          "items": {
            "enum": [
              "web",
              "node",
              "react-native"
            ],
            "type": "string"
          },
          "minItems": 1
        },
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 30 lines
  • check_sdk_setup auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId"
      ],
      "properties": {
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 13 lines
  • create_application auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "organizationId",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1
        },
        "organizationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 19 lines
  • create_flag auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId",
        "name",
        "key",
        "description"
      ],
      "properties": {
        "key": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:[-_][a-z0-9]+)*$",
          "maxLength": 100,
          "minLength": 1
        },
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1
        },
        "description": {
          "anyOf": [
            {
              "type": "string",
              "maxLength": 2000
            },
            {
              "type": "null"
            }
          ]
        },
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 38 lines
  • list_applications auth-required 12h ago

    List the applications in an organization. Flags belong to an application.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "organizationId"
      ],
      "properties": {
        "organizationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 13 lines
  • list_flags auth-required never probed

    List an application's feature flags with whether each is on, and its rollout percent, in every environment.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId"
      ],
      "properties": {
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 13 lines
  • set_flag auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId",
        "flagKey",
        "environment",
        "enabled"
      ],
      "properties": {
        "enabled": {
          "type": "boolean"
        },
        "flagKey": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:[-_][a-z0-9]+)*$",
          "maxLength": 100,
          "minLength": 1
        },
        "environment": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:[-_][a-z0-9]+)*$",
          "maxLength": 100,
          "minLength": 1
        },
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        },
        "rolloutPercent": {
          "type": "number",
          "maximum": 100,
          "minimum": 0
        },
        "confirmProduction": {
          "type": "boolean"
        }
      }
    }
    arguments 39 lines
  • get_user_flags auth-required 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId",
        "environment",
        "user"
      ],
      "properties": {
        "user": {
          "type": "string",
          "maxLength": 256,
          "minLength": 1
        },
        "times": {
          "type": "array",
          "items": {
            "type": "string",
            "format": "date-time"
          },
          "maxItems": 10,
          "minItems": 1
        },
        "environment": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:[-_][a-z0-9]+)*$",
          "maxLength": 100,
          "minLength": 1
        },
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 35 lines
  • get_sdk_docs auth-required 39h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId",
        "environment",
        "platform"
      ],
      "properties": {
        "platform": {
          "enum": [
            "react",
            "react-native",
            "ios",
            "android",
            "browser",
            "node",
            "python",
            "go",
            "java",
            "dotnet",
            "ruby",
            "rust",
            "cpp",
            "php"
          ],
          "type": "string"
        },
        "environment": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:[-_][a-z0-9]+)*$",
          "maxLength": 100,
          "minLength": 1
        },
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 40 lines
  • create_client_key auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "applicationId",
        "environment"
      ],
      "properties": {
        "name": {
          "type": "string",
          "default": "Client key",
          "maxLength": 100,
          "minLength": 1
        },
        "environment": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:[-_][a-z0-9]+)*$",
          "maxLength": 100,
          "minLength": 1
        },
        "applicationId": {
          "type": "string",
          "pattern": "^[1-9]\\d*$"
        }
      }
    }
    arguments 26 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9b8ad9054d3e6bf0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9b8ad9054d3e6bf0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9b8ad9054d3e6bf0/badge.svg)](https://brick.blue/agent/9b8ad9054d3e6bf0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.