MCPJam CLI
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 @mcpjam/cli 6.2.2 (license not stated; repo MCPJam/inspector). Installed pinned with scripts off (npm --ignore-scripts) and launched with `mcp`: initialize and tools/list over stdio succeeded with no credentials and listed 17 tools (17 annotated by the server: 13 read-only, 0 destructive). Real calls: 2 of 2 real function calls passed.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): pass. 2 of 2 real function calls passed. Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 2110 tokens, cl100k estimate (17 tools, measured 2026-11-13 UTC, version 6.2.2). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 10 read, 1 write (state-changing), 6 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
call_tool— unclassifiedconnect_server— unclassifieddisconnect_server— unclassifiedget_notifications— write (state-changing)get_prompt— readget_skill— readlist_prompts— readlist_resources— readlist_servers— readlist_skills— readlist_tools— readping_server— unclassifiedprobe_server— unclassifiedread_resource— readread_skill_file— readserver_doctor— unclassifiedserver_info— read
handshake and tools listed without a recorded key or OAuth
Score 88/100 · Tools 17 · Token cost approx. 2,110 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 6.2.2 · Package @mcpjam/cli · Repo MCPJam/inspector
Summary: MCPJam CLI completed an MCP handshake without credentials and exposed 17 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 17
- Context cost
- approx. 2110 tokens, cl100k estimate (17 tools, measured 2026-11-13 UTC, version 6.2.2; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @mcpjam/cli (Node 20, Linux) succeeded in 3s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 17 tools listed in 11.5s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 2,312 GitHub stars. |
| 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 (NOASSERTION). |
Local-model readiness
Token cost (estimate): approx. 2110 tokens, cl100k estimate for 17 tools · about 26% 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-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 17 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-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
7752673db54e: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@mcpjam/cli",
"version": "6.2.2",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 17,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @mcpjam/cli` (Node 20, Linux) succeeded in 3s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 17 tools listed in 11.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 2,312 GitHub stars."
],
"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 (NOASSERTION)."
]
}
}Install
npx -y @mcpjam/cli mcp
Pin the version we tested
npx -y @mcpjam/cli@6.2.2 mcp
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"mcpjam-cli": {
"command": "npx",
"args": [
"-y",
"@mcpjam/cli@6.2.2",
"mcp"
]
}
}
}Tools listed
connect_server, disconnect_server, list_servers, server_info, ping_server, list_tools, call_tool, list_resources, read_resource, list_skills, get_skill, read_skill_file, list_prompts, get_prompt, get_notifications, server_doctor, probe_server
Quick config
{
"mcpServers": {
"mcpjam-cli": {
"command": "npx",
"args": [
"-y",
"@mcpjam/cli",
"mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @mcpjam/cli(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (17 in our test).
{
"mcpServers": {
"mcpjam-cli": {
"command": "npx",
"args": [
"-y",
"@mcpjam/cli",
"mcp"
]
}
}
}Test history
- 2026-11-13 UTC: New
Related: Best testing and QA MCP servers
FAQ
Is MCPJam CLI deprecated?
No. @mcpjam/cli was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces MCPJam CLI?
Nothing; MCPJam CLI is not deprecated as of 2026-11-13 UTC.
Does MCPJam CLI need an API key?
No. It completed an MCP handshake with no credentials and listed 17 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.