Ext Ops Panel
Open dashboard
Comparison

com.insumermodel/insumer vs Noticer Expected Result Checks

com.insumermodel/insumer is an MCP server published by insumermodel.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Noticer Expected Result Checks is an MCP server published by zensteagarden. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacecom.insumermodel/insumerNoticer Expected Result Checks
Official MCP Registry Listed
Version: 1.23.0
Downloads/month (npm): 4 841
Downloads/week (npm): 2 295
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.3.2-dev.20261016
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.23.0
Downloads/month (npm): 4 841
Downloads/week (npm): 2 295
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed

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

com.insumermodel/insumer vs Noticer Expected Result Checks
Factcom.insumermodel/insumerNoticer Expected Result Checks
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-22 (better)2026-10-16 (worse)
Where it runs (differs)Remote server or your machineOn your machine (https://github.com/zensteagarden/noticer-open/releases/download/noticer-commercial-mcp-v0.3.2-dev.20261016/noticer-commercial-mcp-0.3.2-dev.20261016.mcpb)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Licence (differs)MITNot stated
Repository (differs)github.com/insumerapi/mcp-server-insumergithub.com/zensteagarden/noticer-open
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 21 h agono 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

com.insumermodel/insumer

In its own words, on Official MCP Registry:

Wallet auth: send a wallet and conditions, get a signed boolean across 37 chains.

Noticer Expected Result Checks

In its own words, on Official MCP Registry:

After a handoff, check one public JSON field equals one exact value. Signed receipt. 5 free checks.

How to run each

com.insumermodel/insumer As a remote MCP server

Claude Code
claude mcp add --transport http insumer https://api.insumermodel.com/mcp

Requires: INSUMER_API_KEY (secret), INSUMER_PAYMENT_KEY (secret)

Noticer Expected Result Checks

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

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

Only com.insumermodel/insumer has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of Noticer Expected Result Checks nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of Noticer Expected Result Checks publish no settings it asks for, so we do not compare settings.

What it can do: com.insumermodel/insumer · What it can do: Noticer Expected Result Checks · Compare two other plugins

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