Ext Ops Panel
Open dashboard
Comparison

NoMac (all tools) vs MCPfinder - MCP Server Discovery

NoMac (all tools) is an MCP server published by nomac.app. Marketplaces we read that list it: 1 (Official MCP Registry). MCPfinder - MCP Server Discovery is an MCP server published by mcpfinder.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
MarketplaceNoMac (all tools)MCPfinder - MCP Server Discovery
Official MCP Registry Listed
Version: 1.1.0
No figure published
Not marked · First seen
Listed
Version: 2.0.2
Downloads/month (npm): 1 129
Downloads/week (npm): 198
Forks (GitHub): 5
Stars (GitHub): 13
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.0.2
Downloads/month (npm): 1 129
Downloads/week (npm): 198
Forks (GitHub): 5
Stars (GitHub): 13
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

NoMac (all tools) vs MCPfinder - MCP Server Discovery
FactNoMac (all tools)MCPfinder - MCP Server Discovery
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub13
Forks (GitHub) (differs)No figure on GitHub5
Last release (differs)2026-10-26 (worse)2026-11-03 (better)
Where it runs (differs)Remote server (mcp.nomac.app/all)On your machine (@mcpfinder/server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedAGPL-3.0-or-later
Repository (differs)Not statedgithub.com/mcpfinder/mcpfinder
Changes in the last 7 days (differs)03
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)Responded 10 h ago, requires authenticationno 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

NoMac (all tools)

In its own words, on Official MCP Registry:

Everything NoMac in one server: the Mac, the cloud iPhone and the App Store.

MCPfinder - MCP Server Discovery

In its own words, on Official MCP Registry:

Your AI discovers and installs MCP servers across the Official MCP Registry and Glama.

How to run each

NoMac (all tools) As a remote MCP server

Claude Code
claude mcp add --transport http all https://mcp.nomac.app/all

MCPfinder - MCP Server Discovery As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcpfinder-mcp-server-discovery -- npx -y @mcpfinder/server

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

Only NoMac (all tools) 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: NoMac (all tools) · What it can do: MCPfinder - MCP Server Discovery · 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