Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

reevesagents

NPM · REEVESAGENTS

Spawn, read and steer AI coding CLIs (Claude Code, Codex, Kimi and more) in local tmux windows.

Available components

+3 this week 81 Trust /100

Last scanned (4 hours ago)

Scores higher than 74% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
  • 43 of 140 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to mertkayacs/reevesagents). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2746 tokens (~83/item across 33 items; 31 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kill" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 0
    • Stability: 0.13 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Package version: 1.9.1 → 2.0.0 functional
  • 18 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 17 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 1.9.0 → 1.9.1 functional
  • 16 Oct 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 1.8.2 → 1.9.0 functional
  • 14 Oct 26 +30
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 49 functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Oct 2026 · Analysed npm/reevesagents@2.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo mertkayacs/reevesagents
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mertkayacs/reevesagents/.github/workflows/publish.yml@refs/tags/v2.0.0
Rekor log index 3317035361
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:aeaf8cb0b8c2933c036254686768fb014eff98a09cfaff51ea2d80652f579f72c67000d76a4d5f831be8ea5b75bb42e0e77ba00a81572d5f468504c3e

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall dangerous node -e "try{process.env.npm_config_global==='true'&&process.stdout.isTTY&&!process.env.CI&&process.stdout.write('\nReevesAgents installed. Run: reevesagents attach to connect your AI CLIs, then restart them.\n\n')}catch(e){}"

Background: Why install scripts are a supply-chain risk →

Dependencies 140 packages
Packages resolved 140
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 31 exposed · ~2,355 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
attach_host ~77

Attach the reevesagents MCP to one host CLI by its key (from list_hosts), or to every installed host when key is omitted. After attaching, that CLI can drive agents through these same tools.

NameTypeReqDescription
keystring–Host key from list_hosts, e.g. cc or codex. Omit to attach all installed hosts.

No output schema declared.

No examples provided.

check_approval ~38

Read one approval's current status (pending, approved, denied, or expired) by its approval_id.

NameTypeReqDescription
approval_idstringyes–

No output schema declared.

No examples provided.

delete ~36

Permanently remove one ended agent's record. Kill the agent first; a still-running agent is rejected.

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

delete_history ~31

Permanently remove one archived run history record by its id (from list_history).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

delete_preset ~38

Permanently delete a saved preset by its name (from list_presets). Does not affect any running run.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

delete_run ~41

Permanently remove one ended run, archiving it to history. Stop the run first; a still-running run is rejected.

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

detach_host ~49

Detach the reevesagents MCP from one host CLI by its key (from list_hosts). The CLI keeps running but can no longer drive agents through reevesagents.

NameTypeReqDescription
keystringyes–

No output schema declared.

No examples provided.

doctor ~58

Check this machine for running agents: tmux availability, which provider CLIs are installed, and the state directories. Returns each check with an ok/warn/fail status and a detail string. Run it when a spawn fails to see what is missing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_config ~76

Read the global reevesagents settings: peek_interval_ms, peek_lines, max_depth, max_agents (the per-run agent cap), ready_delay_ms, max_lifetime_ms (auto-reap agents older than this; 0 disables), default_permissions, and language. Check max_agents here when a spawn is rejected for hitting the cap.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

install_skills ~114

Install the reevesagents Agent Skill so skill-aware CLIs (Claude Code, Codex, Kimi, OpenCode) learn to drive reevesagents on their own. Writes one SKILL.md to the two shared skill directories under the home dir. Pass no arguments; call with status omitted to install, or read the returned rows to see where it landed. The user must restart their CLIs to pick it up.

NameTypeReqDescription
statusboolean–When true, only report where the skill is installed without writing anything.

No output schema declared.

No examples provided.

interrupt ~28

Press ctrl-c in one agent to interrupt whatever it is doing.

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

kill ~46

Stop one agent and close its tmux window. Pass an agent_id from spawn or list. Once it is ended you can remove its record with delete.

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

list ~53

List every live run and the agents in each, with their ids, status, provider, and tmux info. Start here to find a run_id or agent_id for the other tools. Ended runs are in list_history.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_approvals ~55

List approval requests, optionally filtered by run_id or status (pending, approved, denied, expired). Use it to find an approval_id to resolve.

NameTypeReqDescription
run_idstring––
statusstring––

No output schema declared.

No examples provided.

list_history ~30

List archived run history: runs that have ended or gone stale. Live runs are in list, not here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_hosts ~51

List the AI CLIs on this machine that can host the reevesagents MCP and whether reevesagents is attached to each. Use it to see where this control surface is wired before attach_host or detach_host.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_presets ~43

List saved run presets: reusable agent-team templates, each with a root agent and workers. Launch a whole team at once by passing a preset name to start_preset.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_providers ~43

List the CLI providers this machine can launch: id, display name, whether it is installed, aliases, and known models. Pass an id as the provider for spawn.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tools ~78

List the helper tool CLIs on this machine (Perplexity, Google Colab, Hugging Face, Ollama): what each is for, whether it is installed, and its state (signed in, or reachable for Ollama), plus an example command and a docs link. They are not spawn providers; run them from your own shell.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open ~107

Open a run or agent in tmux for the user: switch the attached tmux client to a run (its reeves tab) or to a specific agent window. Works for any run, whether this agent started it or not, so you can surface any run for the user on request. No effect when nobody is attached.

NameTypeReqDescription
idstringyesA run id or an agent id (from list). A run id opens its reeves tab; an agent id opens that agent window.

No output schema declared.

No examples provided.

read ~66

Read one agent's recent terminal output, ANSI-stripped and secret-redacted. Use it to see what the agent printed or is waiting on. Defaults to the last 20 lines.

NameTypeReqDescription
agent_idstringyes–
linesnumber–How many lines, default 20.

No output schema declared.

No examples provided.

reap ~120

Sweep for zombie agents and orphan tmux sessions: ends any agent whose tmux window has died or that is older than max_lifetime_ms when that is set above 0 (see get_config), and kills reeves-*/reevesweb_* sessions no live record owns. Returns each reaped agent with the reason (window-gone or lifetime-exceeded) and its age, plus the killed orphan session names. This runs on its own in the background; call it to force an immediate sweep, e.g. after a crash or before relying on list.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_approval ~82

Ask for approval before a risky action. Creates a pending approval that a human or another agent clears with resolve_approval, and returns it with its approval_id.

NameTypeReqDescription
actionstringyes–
agent_idstringyesThe agent asking for approval.
detailsobject––
riskstring––
summarystringyes–

No output schema declared.

No examples provided.

resolve_approval ~55

Approve or deny one pending approval by its approval_id (from list_approvals). An optional note records why.

NameTypeReqDescription
approval_idstringyes–
decisionstringyes–
notestring––

No output schema declared.

No examples provided.

save_preset ~115

Save a live run's agent line-up as a reusable preset under a name, so the same team can be relaunched later with start_preset. Pass a run_id from list. Re-saving the same name updates it. Note: a captured agent's auth_mode and effort are not stored (they default).

NameTypeReqDescription
descriptionstring––
namestringyesPreset name; characters that are not filename-safe are replaced.
run_idstringyesThe run whose agents become the preset (from list).

No output schema declared.

No examples provided.

send_key ~64

Press one key in an agent: enter, escape, tab, space, up, down, left, right, backspace, or ctrl-c. Send enter after send_text to submit the pasted text.

NameTypeReqDescription
agent_idstringyes–
keystringyes–

No output schema declared.

No examples provided.

send_text ~57

Paste text into one agent at its prompt. This does NOT submit it: follow with send_key enter to send. Use it to give a running agent a new instruction.

NameTypeReqDescription
agent_idstringyes–
textstringyes–

No output schema declared.

No examples provided.

set_config ~256

Change one or more global settings and save them. Pass only the fields to change. Counts must be positive integers (ready_delay_ms and max_lifetime_ms may be 0); default_permissions is ask or skip; language is a supported code such as en or tr. Example: raise the per-run agent cap with { "max_agents": 20 }, or auto-kill agents running longer than an hour with { "max_lifetime_ms": 3600000 }. Returns the saved settings.

NameTypeReqDescription
default_permissionsstring–Permission mode used when a spawn omits one.
languagestring–UI language code for the TUI and web UI, e.g. en, tr.
max_agentsnumber–Max agents per run.
max_depthnumber–Spawn recursion cap.
max_lifetime_msnumber–Auto-reap any agent older than this many ms on the next sweep. 0 disables lifetime reaping.
peek_interval_msnumber–Milliseconds between output peek polls.
peek_linesnumber–Lines captured per peek.
ready_delay_msnumber–Delay before the startup prompt is injected.
web_themestring–Web UI appearance.

No output schema declared.

No examples provided.

spawn ~305

Start a CLI agent in its own tmux window and return its agent_id (use it with send_text, send_key, read, kill) and run_id. Omit run_id to add the agent to this MCP session run, created on the first spawn so a chain of spawns stays in one run; pass run_id to add it to an existing run. Call list_providers for valid provider keys.

NameTypeReqDescription
auth_modestring–How the CLI authenticates. Blank uses the provider default.
effortstring–Reasoning effort, for providers that support it. Blank uses the provider default.
extra_argsarray–Extra flags appended verbatim to the launch, for provider options ReevesAgents does not model. Each flag and its value is a separate item, e.g. ["--remote-control"].
modelstring–Model id. Blank keeps the provider default.
namestring–Run name when starting a new run.
nicknamestring––
permissionsstring–ask prompts for each action; skip runs autonomously. Blank uses the global default.
providerstringyesProvider key, e.g. cc, codex, kimi, qwen, opencode, hermes.
run_idstring–Add to this run. Omit to start a new run.
taskstring–Initial prompt pasted into the agent on startup.
working_dirstring––

No output schema declared.

No examples provided.

start_preset ~92

Launch a new run from a saved preset (see list_presets), starting its root agent and every worker at once. Optionally override the run name and working_dir. Returns the new run and its agents.

NameTypeReqDescription
namestringyesPreset name to launch (from list_presets).
run_namestring–Run name; defaults to the preset name.
working_dirstring––

No output schema declared.

No examples provided.

stop ~51

Stop a whole run: end every agent in it and tear down its tmux session. Pass a run_id from spawn or list. Once ended, remove it with delete_run.

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the reevesagents MCP server?

reevesagents runs locally as an npm package, launched with npx -y reevesagents. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · reevesagents

# add to Claude Code
claude mcp add mertkayacs-reevesagents -- npx -y reevesagents
Common questions

What is the reevesagents MCP server?

reevesagents is an MCP server listed in the public MCP registry as io.github.mertkayacs/reevesagents. Spawn, read and steer AI coding CLIs (Claude Code, Codex, Kimi and more) in local tmux windows. This page covers its npm package (reevesagents).

Is the reevesagents MCP server safe to use?

reevesagents scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares an install script we flagged as high risk. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the reevesagents MCP server expose?

reevesagents exposes 31 tools: spawn, kill, stop, send_text, send_key, and 26 more. Their descriptions and schemas cost roughly 2,355 tokens of context every time the server is loaded.

Is the reevesagents MCP server still maintained?

reevesagents is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the reevesagents MCP server under?

reevesagents declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.