NinjaOne MCP vs PulseWatch public knowledge
NinjaOne MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). PulseWatch public knowledge is an MCP server published by pulsewatch.top. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   NinjaOne MCP | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.22 Forks (GitHub): 17 Stars (GitHub): 72 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | NinjaOne MCP | PulseWatch public knowledge |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 72 | No figure on GitHub |
| Forks (GitHub) (differs) | 17 | No figure on GitHub |
| Last release (differs) | 2026-11-05 | Not published |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/ninjaone-v0.1.22/ninjaone-mcp.mcpb) | Remote server (pulsewatch.top/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 12, secrets among them: 5 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/servosity/msp-skills | Not stated |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
NinjaOne MCP
Every NinjaOne report, plus a local store that answers fleet-wide questions no single API call can
PulseWatch public knowledge
Public PulseWatch offers and monitoring guides. No private customer data or monitor controls.
How to run each
NinjaOne MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install ninjaone@msp-skillsRequires: NINJAONE_CLIENT_ID (secret), NINJAONE_CLIENT_SECRET (secret), NINJAONE_MCP_HTTP_TOKEN (secret), NINJAONE_OAUTH_SCOPE (secret), PRINTING_PRESS_CLIENT_PROFILE (secret)
PulseWatch public knowledge As a remote MCP server
claude mcp add --transport http public-knowledge https://pulsewatch.top/mcp/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only PulseWatch public knowledge has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of PulseWatch public knowledge publish no settings it asks for, so we do not compare settings.
What it can do: NinjaOne MCP · What it can do: PulseWatch public knowledge · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.