MCP servers › io.github.mertkayacs › reevesagents

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.mertkayacs/reevesagents

Spawn, read and steer AI coding CLIs (Claude Code, Codex, Kimi and more) in local tmux windows. — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedPricing: open-source · AI-classifiedversion 2.0.0TypeScriptApache-2.0standard input/output31 tools

Summary

io.github.mertkayacs/reevesagents is a local MCP server listed in the official MCP registry at version 2.0.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 31 tools, 2 resources and 0 prompts.

Record checks

9 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#2,031 of 15,112 packages by monthly downloads, tied with 1 other
#773 of 22,952 repositories by GitHub stars, tied with 3 others
#341 of 1,074 packages meeting all 9 record checks, by downloads

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: Apache-2.0
Dependencies: no known high or critical advisories
Repository: public
Tools: 31
Described as changing data: 20 of 31 toolsAI-classified
Mainly works on: files and code on the machine it runs on; cloud accounts, servers or DevOps toolsAI-classified
Topic: developer-toolsAI-classified
Pricing: open-sourceAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

20 tools are described as changing something (spawn, kill, stop, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

2.0.0, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-09 (earliest version still in the registry; older removed versions would be earlier)

Version history

6 versions listed, 2026-10-09 to 2026-10-18; 6 in the 90 days before the 2026-10-23 snapshot.

Most recent 6 versions

2.0.0 · 2026-10-18
1.9.1 · 2026-10-17
1.9.0 · 2026-10-16
1.8.2 · 2026-10-10
1.8.1 · 2026-10-09
1.8.0 · 2026-10-09

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.0.0 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

31tools

2resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; cloud accounts, servers or DevOps tools.

20 of 31 tools are described as changing something (creating, editing, deleting, sending or running).

spawndescribed as changing data
“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.”
11 inputs, 1 required
- run_idstring“Add to this run.”
- providerstringrequired“Provider key, e.g.”
- modelstring“Model id.”
- taskstring“Initial prompt pasted into the agent on startup.”
- nicknamestring
- namestring“Run name when starting a new run.”
- working_dirstring
- permissionsstring“ask prompts for each action; skip runs autonomously.”
- auth_modestring“How the CLI authenticates.”
- effortstring“Reasoning effort, for providers that support it.”
- extra_argsarray“Extra flags appended verbatim to the launch, for provider options ReevesAgents does not model.”
killdescribed as changing data
“Stop one agent and close its tmux window.”
1 input, 1 required
- agent_idstringrequired
stopon 16 other serversdescribed as changing data
“Stop a whole run: end every agent in it and tear down its tmux session.”
1 input, 1 required
- run_idstringrequired
send_texton 5 other serverssends messagesdescribed as changing data
“Paste text into one agent at its prompt.”
2 inputs, 2 required
- agent_idstringrequired
- textstringrequired
send_keydescribed as changing data
“Press one key in an agent: enter, escape, tab, space, up, down, left, right, backspace, or ctrl-c.”
2 inputs, 2 required
- agent_idstringrequired
- keystringrequired
interrupton 1 other serverdescribed as changing data
“Press ctrl-c in one agent to interrupt whatever it is doing.”
1 input, 1 required
- agent_idstringrequired
readon 35 other serversreads or searches
“Read one agent's recent terminal output, ANSI-stripped and secret-redacted.”
2 inputs, 1 required
- agent_idstringrequired
- linesnumber“How many lines, default 20.”
liston 20 other serversreads or searches
“List every live run and the agents in each, with their ids, status, provider, and tmux info.”
Takes no inputs.
list_providerson 42 other serversreads or searches
“List the CLI providers this machine can launch: id, display name, whether it is installed, aliases, and known models.”
Takes no inputs.
list_toolson 48 other serversreads or searches
“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 exam…”
Takes no inputs.
request_approvalon 10 other serversdescribed as changing data
“Ask for approval before a risky action.”
5 inputs, 3 required
- agent_idstringrequired“The agent asking for approval.”
- actionstringrequired
- summarystringrequired
- detailsobject
- riskstring
resolve_approvaldescribed as changing data
“Approve or deny one pending approval by its approval_id (from list_approvals).”
3 inputs, 2 required
- approval_idstringrequired
- decisionstringrequired
- notestring

Show 19 more tools

check_approvalon 5 other serversreads or searches
“Read one approval's current status (pending, approved, denied, or expired) by its approval_id.”
1 input, 1 required
- approval_idstringrequired
list_approvalson 4 other serversreads or searches
“List approval requests, optionally filtered by run_id or status (pending, approved, denied, expired).”
2 inputs
- run_idstring
- statusstring
list_historyon 9 other serversreads or searches
“List archived run history: runs that have ended or gone stale.”
Takes no inputs.
deleteon 12 other serversdeletesdescribed as changing data
“Permanently remove one ended agent's record.”
1 input, 1 required
- agent_idstringrequired
delete_rundeletesdescribed as changing data
“Permanently remove one ended run, archiving it to history.”
1 input, 1 required
- run_idstringrequired
delete_historydeletesdescribed as changing data
“Permanently remove one archived run history record by its id (from list_history).”
1 input, 1 required
- idstringrequired
openon 10 other serverscontrols a browser or desktopdescribed as changing data
“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.”
1 input, 1 required
- idstringrequired“A run id or an agent id (from list).”
doctoron 47 other serversreads or searches
“Check this machine for running agents: tmux availability, which provider CLIs are installed, and the state directories.”
Takes no inputs.
reapdescribed as changing data
“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-*/reevesw…”
Takes no inputs.
get_configon 21 other serversreads or searches
“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), def…”
Takes no inputs.
set_configon 4 other serverscreates or changes datadescribed as changing data
“Change one or more global settings and save them.”
9 inputs
- peek_interval_msnumber“Milliseconds between output peek polls.”
- peek_linesnumber“Lines captured per peek.”
- max_depthnumber“Spawn recursion cap.”
- max_agentsnumber“Max agents per run.”
- ready_delay_msnumber“Delay before the startup prompt is injected.”
- max_lifetime_msnumber“Auto-reap any agent older than this many ms on the next sweep.”
- default_permissionsstring“Permission mode used when a spawn omits one.”
- languagestring“UI language code for the TUI and web UI, e.g.”
- web_themestring“Web UI appearance.”
list_presetson 20 other serversreads or searches
“List saved run presets: reusable agent-team templates, each with a root agent and workers.”
Takes no inputs.
save_preseton 2 other serverscreates or changes datadescribed as changing data
“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.”
3 inputs, 2 required
- run_idstringrequired“The run whose agents become the preset (from list).”
- namestringrequired“Preset name; characters that are not filename-safe are replaced.”
- descriptionstring
start_presetdescribed as changing data
“Launch a new run from a saved preset (see list_presets), starting its root agent and every worker at once.”
3 inputs, 1 required
- namestringrequired“Preset name to launch (from list_presets).”
- run_namestring“Run name; defaults to the preset name.”
- working_dirstring
delete_preseton 1 other serverdeletesdescribed as changing data
“Permanently delete a saved preset by its name (from list_presets).”
1 input, 1 required
- namestringrequired
list_hostson 3 other serversreads or searches
“List the AI CLIs on this machine that can host the reevesagents MCP and whether reevesagents is attached to each.”
Takes no inputs.
attach_hostdescribed as changing data
“Attach the reevesagents MCP to one host CLI by its key (from list_hosts), or to every installed host when key is omitted.”
1 input
- keystring“Host key from list_hosts, e.g.”
detach_hostdescribed as changing data
“Detach the reevesagents MCP from one host CLI by its key (from list_hosts).”
1 input, 1 required
- keystringrequired
install_skillson 1 other servercreates or changes datadescribed as changing data
“Install the reevesagents Agent Skill so skill-aware CLIs (Claude Code, Codex, Kimi, OpenCode) learn to drive reevesagents on their own.”
1 input
- statusboolean“When true, only report where the skill is installed without writing anything.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 31 tools
Says what it returns: 55% of 31 tools
States limits, defaults or errors: 7% of 29 tools
Says when to use it: 17% of 30 tools
Items covered per tool: 1.8 of 4 on average

Counted from the listing

Parameters with a description: 50% of 54
Tools with a description: 100% of 31
Typical description length: 193 characters

The tool set

Counted from the listing

Tools: 31
Size of the list: about 3,242 tokens for an agent to load (characters ÷ 4)
Naming: 21 of 31 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 31 of 31 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package reevesagents

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "reevesagents": {
      "command": "npx",
      "args": [
        "-y",
        "reevesagents@2.0.0",
        "mcp"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "reevesagents": {
      "command": "npx",
      "args": [
        "-y",
        "reevesagents@2.0.0",
        "mcp"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "reevesagents": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "reevesagents@2.0.0",
        "mcp"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"reevesagents","type":"stdio","command":"npx","args":["-y","reevesagents@2.0.0","mcp"]}'

Claude Code

claude mcp add --transport stdio reevesagents -- npx -y reevesagents@2.0.0 mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y reevesagents@2.0.0 mcp

Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 2.0.0
Latest stable: 2.0.0
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-rq+MsLjCkzwDYlRoZ…
Signature: signed and attested
License: Apache-2.0

Source: the package registry · 2026-10-23.

Usage

Downloads: 1,265 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 2.0.0 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/mertkayacs/reevesagents	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.mertkayacs
GitHub owner: a personal account (mertkayacs)
Build record: signed and attested

Repository: github.com/mertkayacs/reevesagents
Stars: 107
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no
Security policy: .github/SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

#2,031 of 15,112 packages by monthly downloads, tied with 1 other
#773 of 22,952 repositories by GitHub stars, tied with 3 others
#341 of 1,074 packages meeting all 9 record checks, by downloads

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierApache-2.0
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.mertkayacs/reevesagents

Answered from the data above

Is io.github.mertkayacs/reevesagents safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 20 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.mertkayacs/reevesagents free to use?

Its website (reevesagents.mertkayacs.com/) describes a open-source pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.github.mertkayacs/reevesagents been security tested?

Partly. 3 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.mertkayacs/reevesagents do?

It lists 31 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.mertkayacs/reevesagents change or delete data?

20 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.mertkayacs/reevesagents publish a security policy?

Yes: its repository has a public security policy (github.com/mertkayacs/reevesagents/blob/HEAD/.github/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 2.0.0, the latest stable release on npm.

Where is the source code of io.github.mertkayacs/reevesagents?

In github.com/mertkayacs/reevesagents, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.callstack/agent-deviceagent-devicealso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.A9T9/uivision-mcpUi.Vision MCPalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.tomyud1/godot-mcpalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.sapiom/mcpalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.zebbern/webhook-mcp-serverWebhook.site MCP Serveralso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searches, sends messagescompare with this one
io.github.enessubass/mobiloop-mcpMobiLoopalso has tools that controls a browser or desktop, creates or changes data, deletes, reads or searches, sends messagescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

3 exercised9 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
6,227 msConnected after 0 redirects.
Read the inventory: 31 tools, 2 resources, 0 prompts.
17,077 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

open-source

read from reevesagents.mertkayacs.com/ · 2026-10-23

“Apache-2.0 license. Free to use, change and share. Source on GitHub.”

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

1,265 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 100–999 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.mertkayacs/reevesagents: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.mertkayacs/reevesagents

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.mertkayacs/reevesagents)](https://protocolprobe.com/mcp/servers/io.github.mertkayacs/reevesagents)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology