Ext Ops Panel
Open dashboard
Comparison

Liongard MCP vs toolprint by JEStats

Liongard MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). toolprint by JEStats is an MCP server published by jestatsio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
MarketplaceLiongard MCPtoolprint by JEStats
Official MCP Registry Listed
Version: 0.1.7
Forks (GitHub): 13
Stars (GitHub): 64
Not marked · First seen
Listed
Version: 0.4.1
Downloads/month (npm): 220
Downloads/week (npm): 109
Forks (GitHub): 0
Stars (GitHub): 0
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

Liongard MCP vs toolprint by JEStats
FactLiongard MCPtoolprint by JEStats
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)64 (better)0 (worse)
Forks (GitHub) (differs)13 (better)0 (worse)
Last release (differs)2026-10-23 (better)2026-10-15 (worse)
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/liongard-v0.1.7/liongard-mcp.mcpb)On your machine (toolprint)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 32, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/servosity/msp-skillsgithub.com/jestatsio/toolprint
Changes in the last 7 days (differs)60
First seen (differs)2026-10-112026-10-15

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

Liongard MCP

In its own words, on Official MCP Registry:

Liongard config visibility: sync your estate offline, then drift-check and search it from one CLI.

toolprint by JEStats

In its own words, on Official MCP Registry:

package-lock.json for MCP trust: catch MCP rug-pulls, tool poisoning, and leaked secrets.

How to run each

Liongard MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install liongard@msp-skills

Requires: LIONGARD_ACCESS_KEY_ID (secret), LIONGARD_ACCESS_KEY_SECRET (secret), LIONGARD_API_KEY (secret), LIONGARD_INSTANCE

toolprint by JEStats As a local MCP server: npm package

Claude Code
claude mcp add --env "TOOLPRINT_BEARER=<YOUR_TOOLPRINT_BEARER>" --transport stdio toolprint -- npx -y toolprint serve

Requires: TOOLPRINT_BEARER (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Liongard MCP asks for

  • LIONGARD_ACCESS_KEY_ID (secret)
  • LIONGARD_ACCESS_KEY_SECRET (secret)
  • LIONGARD_API_KEY (secret)
  • LIONGARD_BASE_URL
  • LIONGARD_INSTANCE

Only toolprint by JEStats asks for

  • TOOLPRINT_BEARER (secret)
  • TOOLPRINT_WORKDIR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Liongard MCP · What it can do: toolprint by JEStats · 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.

Where the data comes from: how the catalog is built