Opine vs Signal Leads
Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Signal Leads is an MCP server published by botrecipe.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |   Opine | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:e6e704c00f78 Forks (GitHub): 4 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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 | Opine | Signal Leads |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (codygreen719/opine-mcp-server) | Remote server (leads.cloudforbots.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 11 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/cody-docker/opine-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 34 h ago |
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
Opine
A Model Context Protocol (MCP) server for querying deals and evaluations from the Opine CRM API.
Signal Leads
25 sales leads with a public funding, hiring or tech signal, source link and draft message each.
How to run each
Opine As a local MCP server: Docker image
claude mcp add --env "OPINE_API_KEY=<YOUR_OPINE_API_KEY>" --transport stdio opine-mcp-server -- docker run -i --rm -e OPINE_API_KEY codygreen719/opine-mcp-serverRequires: OPINE_API_KEY (secret)
Signal Leads As a remote MCP server
claude mcp add --transport http leads https://leads.cloudforbots.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Signal Leads has a remote endpoint we check. How we check endpoints
Tools each declares
Only Opine has
create_deal_notecreate_ticketdescribe_deal_sales_processget_dealget_salesforce_deallist_dealslist_evaluationslist_sales_process_stageslist_sales_processeslist_ticketsupdate_ticket
Only Signal Leads has
signal_leads_offersignal_leads_resultsusage_and_upgrade
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Signal Leads as of 2026-10-21). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Signal Leads publish no settings it asks for, so we do not compare settings.
What it can do: Opine · What it can do: Signal Leads · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.