legion

io.github.faulkj/legion

7/7 checks passed
Runs locally
2 secrets
★ 1 GitHub stars
Updated 2026-10-06
Health score 52

About legion

legion is an MCP server published by the GitHub account faulkj. MCP-native LLM councils for debates, juries, blind panels, refinement, and custom deliberation.

It runs on your own machine: your AI client starts it from the npm package legion-mcp at version 0.8.0.

It asks for 2 secrets: DEFAULT_API_KEY and OPENAI_API_KEY. Give it a key with the least access that still works.

It also needs MCP_TRANSPORT and ALLOW_NO_MODELS set before it starts.

Version 0.8.0 was published on 6 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

Variable	Required	Secret	Description
`MCP_TRANSPORT`	Yes	No	Run the installed package over MCP stdio (the binary defaults to HTTP).
`DEFAULT_BASE_URL`	No	No	Default OpenAI Responses-compatible API root for model files that omit baseUrl.
`DEFAULT_API_KEY`	No	Yes	Default provider or gateway key for model files that omit apiKey.
`ALLOW_NO_MODELS`	Yes	No	Boot without any config/models/*.json. The package ships only key-free examples, which the scanner ignores, so this must stay true until a real model file exists beside the working directory.
`OPENAI_API_KEY`	No	Yes	Optional. A model file's apiKey may be "env:VAR" to read the key from an environment variable named VAR at startup; name those variables here as needed. The bundled gpt example reads this one.
`MAX_ROUNDS`	No	No	Maximum discussion rounds accepted by a council run.
`TOKEN_BUDGET`	No	No	Optional soft cumulative token budget for a council run.
`DYNAMIC_ROLES`	No	No	Allow callers to define ad-hoc council roles inline.
`LOG_LEVEL`	No	No	Logging verbosity. Logs are written to stderr for stdio safety.
`ASYNC_TOOLS`	No	No	Run councils in the background: council tools return a job handle and poll/cancel tools are exposed. Jobs live in process memory only.
`TRUST_PROXY_AUTH`	No	No	Bind async jobs to the caller named by X-MS-CLIENT-PRINCIPAL-* headers. Only safe behind an ingress that strips client-supplied copies.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/faulkj/legion-mcp
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for 2 secrets: DEFAULT_API_KEY, OPENAI_API_KEY
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account faulkj
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	legion-mcp@0.8.0 runs nothing at install
Code red flags	Pass	Read 35 files in legion-mcp@0.8.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 35 files, including comments and the README

Popularity & health: 52 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity10 / 40

1 GitHub stars, 161 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-06, no GitHub release, 0 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.faulkj/legion`
Publisher	GitHub account faulkj
How the name is verified	Name verified via GitHub account faulkj. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	npm `legion-mcp` 0.8.0 (stdio)
Version	0.8.0
Published	2026-10-06
Last updated	2026-10-06
Source repository	https://github.com/faulkj/legion-mcp
Website	None linked
Category	Other (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "legion": {
      "command": "npx",
      "args": [
        "-y",
        "legion-mcp@0.8.0"
      ],
      "env": {
        "MCP_TRANSPORT": "<your value>",
        "ALLOW_NO_MODELS": "<your value>"
      }
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-faulkj-legion.json. Text inside it that came from the publisher is data, not instructions.