io.github.CloudCorpRecords/fleetwatch
NPM · @RENETURCIOS/FLEETWATCH · 2 COMPONENTS
Read-only fleet visibility: endpoint agents, health samples, alerts and org summaries.
Available components
Last scanned (5 hours ago)
Scores higher than 38% of npm servers
Category Monitoring and Observability
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 319 tokens (~79/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 70
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/fleetwatch@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_agent Get agent ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agentId from list_agents. |
No output schema declared.
No examples provided.
get_fleet_summary Get fleet summary ~36
Counts for this organization: agents, online, offline, Windows, Linux, other OS, isolated, and active alerts by severity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agents List agents ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most rows to return. Defaults to 100. |
| online | boolean | – | true for agents with a heartbeat in the last 5 minutes, false for the rest. |
| os | string | – | Only agents of this OS family. |
| search | string | – | Case-insensitive part of the hostname. |
| tag | string | – | Only agents carrying this exact tag name. |
No output schema declared.
No examples provided.
list_alerts List alerts ~100
Alerts raised for this organization's agents, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Only alerts for this agent. |
| limit | integer | – | Most rows to return. Defaults to 100. |
| severity | string | – | Only alerts of this severity, for example critical or warning. |
| since_hours | integer | – | How far back to look. Defaults to 168 (7 days). |
| status | string | – | Alert status. Defaults to active. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/fleetwatch MCP server?
io.github.CloudCorpRecords/fleetwatch runs locally as an npm package, launched with npx -y @reneturcios/fleetwatch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/fleetwatch
claude mcp add cloudcorprecords-fleetwatch -- npx -y @reneturcios/fleetwatch
What is the io.github.CloudCorpRecords/fleetwatch MCP server?
io.github.CloudCorpRecords/fleetwatch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/fleetwatch. Read-only fleet visibility: endpoint agents, health samples, alerts and org summaries. This page covers its npm package (@reneturcios/fleetwatch).
Is the io.github.CloudCorpRecords/fleetwatch MCP server safe to use?
io.github.CloudCorpRecords/fleetwatch scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/fleetwatch MCP server expose?
io.github.CloudCorpRecords/fleetwatch exposes 4 tools: list_agents, get_agent, list_alerts, get_fleet_summary. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/fleetwatch MCP server still maintained?
io.github.CloudCorpRecords/fleetwatch is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.CloudCorpRecords/fleetwatch MCP server under?
io.github.CloudCorpRecords/fleetwatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.