Ext Ops Panel
Open dashboard
Comparison

io.github.fpetitit/mcpcheckup vs MCPSentinel

io.github.fpetitit/mcpcheckup is an MCP server published by fpetitit. Marketplaces we read that list it: 1 (Official MCP Registry). MCPSentinel is an MCP server published by gentaArnezzi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplaceio.github.fpetitit/mcpcheckupMCPSentinel
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.8.8
Downloads/month (PyPI): 414
Downloads/week (PyPI): 62
Forks (GitHub): 0
Stars (GitHub): 1
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

io.github.fpetitit/mcpcheckup vs MCPSentinel
Factio.github.fpetitit/mcpcheckupMCPSentinel
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcpcheckup.xyz/api/mcp)On your machine (mcp-guardian-scan)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/fpetitit/mcpcheckgithub.com/gentaarnezzi/mcpsentinel
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-15no remote endpoint we check

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

io.github.fpetitit/mcpcheckup

In its own words, on Official MCP Registry:

Scans remote MCP servers for protocol, security, and TLS issues; exposes scan tools via MCP.

MCPSentinel

In its own words, on Official MCP Registry:

Precision-first security scanning for Model Context Protocol servers.

How to run each

io.github.fpetitit/mcpcheckup As a remote MCP server

Claude Code
claude mcp add --transport http mcpcheckup https://mcpcheckup.xyz/api/mcp

MCPSentinel As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MCPSENTINEL_ALLOWED_HOSTS=<YOUR_MCPSENTINEL_ALLOWED_HOSTS>" --transport stdio mcpsentinel -- uvx mcp-guardian-scan

Requires: MCPSENTINEL_ALLOWED_HOSTS

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

Only io.github.fpetitit/mcpcheckup 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 io.github.fpetitit/mcpcheckup publish no settings it asks for, so we do not compare settings.

What it can do: io.github.fpetitit/mcpcheckup · What it can do: MCPSentinel · Compare two other plugins

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