mbcli MCP (MightyBot)
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs10/15
- License3/10
Tested npm @mightybot/mbcli 0.6.92 (UNLICENSED; no source repo linked in package metadata). Installed pinned with scripts off (npm --ignore-scripts) and launched with `mcp`: initialize and tools/list over stdio succeeded with no credentials and listed 15 tools (no tool annotations). Real calls: 3 of 3 real function calls passed.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): pass. 3 of 3 real function calls passed. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 2000 tokens, cl100k estimate (15 tools, measured 2026-11-18 UTC, version 0.6.92). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 5 read, 2 write (state-changing), 8 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
mightybot.analytics.users— unclassifiedmightybot.docs.list_topics— readmightybot.docs.lookup— readmightybot.docs.read_topic— readmightybot.lifecycle.operation— unclassifiedmightybot.openapi.lookup— readmightybot.single_pane_of_glass— unclassifiedmightybot.start_here— write (state-changing)mightybot.workflow.apply_step_change— unclassifiedmightybot.workflow.check_schemas— write (state-changing)mightybot.workflow.next_operations— unclassifiedmightybot.workflow.orient— unclassifiedmightybot.workflow.plan_change— unclassifiedmightybot.workflow.resolve— readmightybot.workflow.step— unclassified
handshake and tools listed without a recorded key or OAuth
Score 88/100 · Tools 15 · Token cost approx. 2,000 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.6.92 · Package @mightybot/mbcli
Summary: mbcli MCP (MightyBot) completed an MCP handshake without credentials and exposed 15 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 15
- Context cost
- approx. 2000 tokens, cl100k estimate (15 tools, measured 2026-11-18 UTC, version 0.6.92; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @mightybot/mbcli --ignore-scripts (Node v24.22.1, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 15 tools listed in 5.5s. |
| maintenance | pass | 25 | Latest release published 0 days before test. |
| docs | partial | 10 | README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package). |
| license | partial | 3 | License not machine-detected as OSI (UNLICENSED). |
Local-model readiness
Token cost (estimate): approx. 2000 tokens, cl100k estimate for 15 tools · about 24% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 15 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
bb68978959fe: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@mightybot/mbcli",
"version": "0.6.92",
"registry": "npm",
"status": "working",
"tested": "2026-11-18",
"tools_count": 15,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"`npm install @mightybot/mbcli --ignore-scripts` (Node v24.22.1, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 15 tools listed in 5.5s."
],
"maintenance": [
"pass",
25,
"Latest release published 0 days before test."
],
"docs": [
"partial",
10,
"README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"partial",
3,
"License not machine-detected as OSI (UNLICENSED)."
]
},
"testedAt": "2026-11-18T04:19:17.037Z"
}Install
npx -y @mightybot/mbcli mcp
Pin the version we tested
npx -y --ignore-scripts @mightybot/mbcli@0.6.92 mcp
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"mbcli-mightybot-mcp": {
"command": "npx",
"args": [
"-y",
"@mightybot/mbcli@0.6.92",
"mcp"
]
}
}
}Tools listed
mightybot.start_here, mightybot.single_pane_of_glass, mightybot.workflow.resolve, mightybot.workflow.orient, mightybot.workflow.check_schemas, mightybot.analytics.users, mightybot.workflow.step, mightybot.workflow.plan_change, mightybot.workflow.next_operations, mightybot.workflow.apply_step_change, mightybot.docs.lookup, mightybot.docs.list_topics, mightybot.docs.read_topic, mightybot.lifecycle.operation, mightybot.openapi.lookup
Quick config
{
"mcpServers": {
"mbcli-mightybot-mcp": {
"command": "npx",
"args": [
"-y",
"@mightybot/mbcli",
"mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @mightybot/mbcli --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (15 in our test).
{
"mcpServers": {
"mbcli-mightybot-mcp": {
"command": "npx",
"args": [
"-y",
"@mightybot/mbcli",
"mcp"
]
}
}
}Test history
- 2026-11-18 UTC: New
Related: Best dev MCP servers · Troubleshooting: Protocol version mismatch (HTTP 400)
FAQ
Is mbcli MCP (MightyBot) deprecated?
No. mbcli MCP (MightyBot) was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces mbcli MCP (MightyBot)?
Nothing; mbcli MCP (MightyBot) is not deprecated as of 2026-11-18 UTC.
Does mbcli MCP (MightyBot) need an API key?
No. It completed an MCP handshake with no credentials and listed 15 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.