Ext Ops Panel
Open dashboard
Comparison

freshprobe vs HTTP

freshprobe is a plugin bundle for AI coding tools published by Sudhan30. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplacefreshprobeHTTP
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 184
Downloads/week (npm): 31
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

freshprobe vs HTTP
FactfreshprobeHTTP
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@abhishekmcp/http)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)3Not a bundle
LicenceMITMIT
Repository (differs)github.com/sudhan30/freshprobegithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11

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

freshprobe

In its own words, on Claude Code: claude-plugins-community:

Data freshness and endpoint liveness verification for AI agents. Probes external APIs and endpoints before agents act on their data, returning deterministic FRESH/STALE/UNKNOWN verdicts with confidence scores. Analyzes HTTP cache headers, measures latency percentiles (P50/P95/P99), fingerprints content for change detection, checks TLS certificate health, and evaluates against configurable freshness policies. Exposes three MCP tools (freshprobe_check, freshprobe_batch, freshprobe_policy) and includes a built-in skill and agent for contextual triggering. NIST AI RMF aligned. Single Go binary, MIT licensed.

HTTP

In its own words, on Official MCP Registry:

HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.

How to run each

freshprobe As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install freshprobe@claude-community

HTTP As a local MCP server: npm package

Claude Code
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/http

Requires: HTTP_ALLOW_HOSTS

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

The marketplaces of freshprobe publish no settings it asks for, so we do not compare settings.

What it can do: freshprobe · What it can do: HTTP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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