Ext Ops Panel
Open dashboard
Comparison

sniffmcp-cli vs ActionGuard Protocol Inspector Agent

sniffmcp-cli is an MCP server published by SomehowLiving. Marketplaces we read that list it: 1 (PyPI (MCP servers)). ActionGuard Protocol Inspector Agent is an MCP server published by lsendel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacesniffmcp-cliActionGuard Protocol Inspector Agent
PyPI (MCP servers) Listed
Version: 0.5.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 406
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 1
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

sniffmcp-cli vs ActionGuard Protocol Inspector Agent
Factsniffmcp-cliActionGuard Protocol Inspector Agent
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (sniffmcp-cli)Remote server (actionguard.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/somehowliving/sniffmcpgithub.com/lsendel/actionguard
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-21
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 40 h ago returned HTTP 200

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

sniffmcp-cli

In its own words, on PyPI (MCP servers):

Sniff out what your AI tools are hiding: local security checks for MCP servers (hidden instructions, known malware, leaked secrets, rug pulls).

ActionGuard Protocol Inspector Agent

In its own words, on Official MCP Registry:

Diff and poisoning detection for MCP servers: catch schema drift and prompt poisoning.

How to run each

sniffmcp-cli

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

ActionGuard Protocol Inspector Agent As a remote MCP server

Claude Code
claude mcp add --transport http actionguard https://actionguard.ai/mcp

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

Only ActionGuard Protocol Inspector Agent 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

Neither one's marketplaces publish the settings it asks for.

What it can do: sniffmcp-cli · What it can do: ActionGuard Protocol Inspector Agent · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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