List your agent

Railflag

MCP server● Hosted · onlinev0.1.0

Create, target and roll out feature flags. Production changes wait for a person to approve

Reviews

No review yet. Used Railflag? Be the first to help others choose.

What it does

Railflag is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.1.0
PriceNot in the registry
First seen19 Nov 2026
Last checked2d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 6h ago (live check)

Hosted endpoint

  • https://mcp.railflag.com/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "railflag": {
      "url": "https://mcp.railflag.com/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Reliability

Re-tested about every 3 days · last check 6h ago
Insufficient observations2 conclusive checks in 30 days; a figure is shown from 10
2 / 0Answers / failures, 30 days
No key neededAccess status (latest answer)
Observed test history · one mark = one check
19 Nov21 Nov
AnsweredAnswered, key requiredNo valid answer

Observed endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 19 Nov 2026). How we measure

Tool changes

Tool tracking since 20 Nov 2026 · test history since 19 Nov 2026

No tool added or removed since tracking started. 29 tools in the latest list.

Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.

Live check

Electra Index connected to the hosted endpoint 6h ago

ONLINE Railflag answered an MCP connection on 21 Nov 2026 and introduced itself as railflag 0.1.0 (MCP protocol 2025-06-18).

29 tools offered to AI assistants

  • list_flags · All flags with their state in each environment.
  • get_flag · One flag: variations and full targeting in every environment, with versions for safe updates.
  • list_environments · Environments, whether they require approval, and their published config versions. Keys are not returned.
  • create_flag · Creates a flag, off in every environment. Boolean flags have variations [false, true].
  • toggle_flag · Turns a flag on or off in one environment. In environments that need approval this returns an approvalUrl for a person.
  • update_targeting · Replaces a flag's targeting in one environment. Read it with get_flag first and pass its version as baseVersion so you never overwrite someone else's change. Rules are checked top to bottom; the first match wins.
  • set_rollout · Sets the percentage split for the default rule, or for one rule by id. percentages has one number per variation and must add up to 100 (e.g. [80, 20] gives 20% true for a boolean flag). Raising a percentage only adds users.
  • get_history · Audit log for the project or one flag: who changed what, when and why.
  • get_change_request · Status of a change waiting for approval: pending, applied, rejected or failed.
  • suggest_watch_plan · Drafts a Release Watch plan for a flag change: which signals to monitor (error rate, latency, conversions, new Sentry issues, the rollout split), the limits, and for how long. Describe the change with percentages (default rule split, like s
  • get_watch · A watch: its status (draft, active, passed, paused, stopped), each signal's state, the timeline and the verdict.
  • list_watches · Watches in the project, newest first, optionally for one flag and by status (comma separated: draft, active, passed, paused, stopped, expired).
Show 17 more
  • stop_watch · Stops watching. Doesn't change the flag.
  • monitoring_coverage · The project's monitoring coverage: live Production flags nobody watches (ranked by risk), kill switches never tested, flags no SDK evaluates, and services missing error or latency metrics. Business plan.
  • connect_monitoring · Starts connecting Prometheus/Grafana, Datadog, Sentry, New Relic or a Slack channel for alerts. Returns a one-time link: give it to the user, who enters the credentials there. Never ask the user for credentials in chat. Admins only.
  • list_sources · Vendors Railflag can import flags from, what it reads from each, and which are coming later.
  • connect_source · Starts a read-only connection to the user's account at another flag vendor (see list_sources). Returns a link the user opens to enter their credentials there. Never ask the user to paste credentials into the chat. After they finish, call ge
  • get_connection · Whether the user finished connecting, which source environments are visible, and whether decisions can be compared.
  • scan_source · Reads all flags and their targeting from the connected vendor (read only). Runs in the background: poll get_run with the returned runId.
  • get_run · Status and result of a scan, compare or apply run.
  • plan_migration · Builds a dry-run plan from the latest scan. envMap maps source environment ids (from get_connection or the scan) to Railflag environment keys, e.g. {"production": "staging"} to try production data in staging first. Nothing is written.
  • get_plan · A plan's summary, issues and items. full=true includes each item's targeting.
  • explain_item · The source vendor's definition of one flag next to what it becomes in Railflag, and its issues.
  • update_plan · Records decisions on issues. Each issue lists its allowed actions: skip_flag, drop_rule, keep, rename (value = new key), overwrite. Info issues need no decision. Ask the user when the choice is not obviously safe.
  • compare_decisions · Asks the source vendor what sample users get (AB Tasty: Decision API, needs a Decision API key on the connection; Unleash: its server-side playground) without recording anything, and compares with the plan. Runs in the background: poll get_
  • apply_plan · Writes the plan into one Railflag environment. Running it again changes nothing. Environments that need approval return an approvalUrl for a person. Never writes to the source vendor.
  • rollback_run · Undoes one apply run: restores previous targeting and archives flags it created.
  • disconnect_source · Deletes the stored credentials for a source connection.
  • get_code_guide · How to rewrite the source vendor's SDK calls to OpenFeature with Railflag: setup, regex patterns, before/after examples, notes. Apply it in the user's repo yourself and show them the diff.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.railflag.com/mcpDECLAREDSRC-001 Official MCP Registry2d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2d ago
Websitehttps://railflag.com/mcpDECLAREDSRC-001 Official MCP Registry2d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2d ago
Version0.1.0DECLAREDSRC-001 Official MCP Registry2d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2d ago

Change history

  • NEW19 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Railflag? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor RailflagLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Railflag?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/railflag?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/railflag/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Railflag

How do I connect Railflag?

Use the hosted endpoint https://mcp.railflag.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Railflag need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Railflag offer?

When Electra Index connected on 21 Nov 2026, it listed 29 tools: list_flags, get_flag, list_environments, create_flag, toggle_flag, update_targeting, set_rollout, get_history and more. The full list is in "Live check" above.

Is Railflag online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 6h ago.