Feature flags for Next.js. One file, full control.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
flagpost_initCreates flagpost.config.ts in a project directory. Scaffolds a starter config with an example feature flag.Creates flagpost.config.ts in a project directory. Scaffolds a starter config with an example feature flag.
No input schema was published for this tool.
flagpost_add_flagAdds a new feature flag definition to an existing flagpost.config.ts file.Adds a new feature flag definition to an existing flagpost.config.ts file.
No input schema was published for this tool.
flagpost_list_flagsLists all feature flags defined in a flagpost.config.ts file, showing their names and default values.Lists all feature flags defined in a flagpost.config.ts file, showing their names and default values.
No input schema was published for this tool.
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Feature flags for Next.js. One file, full control.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.