Fleetwatch

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 7, 2026

Read-only fleet visibility: endpoint agents, health samples, alerts and org summaries.

概览

AI 生成的概览

连接 ET Ducky 托管 MCP 服务器的只读桥接工具,让助手列出终端代理、查看健康状况、浏览告警并汇总组织终端机群。

可以做什么
  • 按主机名、操作系统、在线状态和标签列出并筛选终端代理
  • 查看单个代理的最新健康采样与活跃告警数量
  • 按状态、严重级别、代理和时间范围查看告警
  • 获取组织级统计:代理数量、系统分布、隔离状态及各严重级别的告警数
适用场景
适合需要让助手回答 Windows/Linux 终端机群相关问题的场景,例如哪些机器在线、健康状况如何、有哪些未处理告警,同时不授予任何写入权限。
运行要求
通过 npx(需 Node.js)或 Docker 镜像以 stdio 在本地运行。可选设置 ETDUCKY_MCP_URL 覆盖上游地址(默认指向 ET Ducky 托管服务器),设置 ETDUCKY_API_KEY 后向上游发送 Bearer 令牌;未设置时不发送认证头。需要能访问上游的网络。
安装前请注意
所有请求都发往第三方 ET Ducky 托管端点,包括主机名、最后登录用户和健康数据。ETDUCKY_API_KEY 会作为 Bearer 令牌发送到 ETDUCKY_MCP_URL 指向的地址,因此只应把该地址改为可信端点。接口为只读,但上游错误文本会原样返回。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Fleetwatch,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

fleetwatch

fleetwatch is a small local bridge to ET Ducky's hosted MCP server, which watches over an organisation's fleet of endpoint agents — the Windows and Linux machines running the ET Ducky agent — and reports who is online, how each machine's health looks, and which alerts are open.

The bridge keeps no fleet data and runs no checks of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. The whole captured surface is read-only: this rebuild adds no write capability.

Tools

  • list_agents — enumerate the organisation's agents with OS, agent version, online state, last heartbeat, last signed-in user, isolation state and tags, sorted by hostname. All arguments are filters: search (a case-insensitive part of the hostname), os (windows, linux or other), online (true for agents with a heartbeat in the last 5 minutes), tag (one exact tag name), and limit (1-500, default 100).
  • get_agent — one agent in full: its latest health sample (CPU, memory, free space on C:, uptime, pending reboot, make and model) and its count of active alerts. Required: agent_id, the id from list_agents.
  • list_alerts — alerts raised for the organisation's agents, newest first. Optional: status (active, acknowledged, resolved, auto_resolved, suppressed or any; defaults to active), severity (for example critical or warning), agent_id to scope to one machine, since_hours (1-720, default 168 — seven days) and limit (1-500, default 100).
  • get_fleet_summary — the organisation at a glance: agent counts, online and offline, the Windows / Linux / other OS split, isolated agents, and active alerts by severity. No arguments.

Configuration

  • ETDUCKY_MCP_URL (optional) — override the upstream endpoint. Defaults to https://etducky.com/api/mcp. (The override hook is this rebuild's own labelled reconstruction.)
  • ETDUCKY_API_KEY (optional) — when set, every upstream request carries an Authorization: Bearer <key> header. When it is not set, no auth header is sent. (This forwarding is also a labelled reconstruction; the original surface was captured keyless.)

Forwarding mechanics

On the first tool call the client opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name fleetwatch), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with fleetwatch error: (this rendering is this rebuild's own labelled reconstruction).

CLI

Each tool is also a subcommand taking one JSON argument string (omit it for tools that take none):

bash
npx @reneturcios/fleetwatch list_agents '{"os":"windows","online":true}'npx @reneturcios/fleetwatch get_agent '{"agent_id":"agent-42"}'npx @reneturcios/fleetwatch get_fleet_summarynpx @reneturcios/fleetwatch --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

bash
npx -y @reneturcios/fleetwatch mcp

MCP client config:

json
{  "mcpServers": {    "fleetwatch": {      "command": "npx",      "args": ["-y", "@reneturcios/fleetwatch", "mcp"]    }  }}

Docker

bash
docker run -i ghcr.io/cloudcorprecords/fleetwatchdocker run --rm ghcr.io/cloudcorprecords/fleetwatch --version

The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.

Development

bash
npm installnpm run buildnpm testnpm run dev

The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.

License

MIT — see LICENSE.

来源:README.md,提交 ad8438b

工具

4

list_agents

List agents

List this organization's ET Ducky agents (Windows and Linux endpoints) with OS, agent version, online state, last heartbeat, last signed-in user, isolation state and tags. Sorted by hostname.

输入参数ostaglimitonlinesearch

get_agent

Get agent

One agent with its latest health sample (CPU, memory, free space on C:, uptime, pending reboot, make and model) and its number of active alerts.

输入参数agent_id必填

list_alerts

List alerts

Alerts raised for this organization's agents, newest first.

输入参数limitstatusagent_idseveritysince_hours

get_fleet_summary

Get fleet summary

Counts for this organization: agents, online, offline, Windows, Linux, other OS, isolated, and active alerts by severity.

无需输入参数。

版本历史

1
  1. v0.1.0最新Nov 4, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分