freshprobe vs Ecosystem Monitor
freshprobe is a plugin bundle for AI coding tools published by Sudhan30. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Ecosystem Monitor is an MCP server published by memoryapi.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  freshprobe | |
|---|---|---|
| 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: 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 | freshprobe | Ecosystem Monitor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (monitor.memoryapi.org/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sudhan30/freshprobe | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
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.
Ecosystem Monitor
Ecosystem monitoring: service status and x402 activity metrics
How to run each
freshprobe As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install freshprobe@claude-communityEcosystem Monitor As a remote MCP server
claude mcp add --transport http monitor https://monitor.memoryapi.org/mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: freshprobe · What it can do: Ecosystem Monitor · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.