Ext Ops Panel
Open dashboard
Comparison

Zocks Advisor Intelligence vs LayerCall

Zocks Advisor Intelligence is a plugin bundle for AI coding tools published by zocks-communications. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). LayerCall is an MCP server published by layercall.com. 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

Where each is published
MarketplaceZocks Advisor IntelligenceLayerCall
Claude Code: claude-plugins-official Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

Zocks Advisor Intelligence vs LayerCall
FactZocks Advisor IntelligenceLayerCall
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.zocks.io/mcp)Remote server (www.layercall.com/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
Licence (differs)LicenseRef-Zocks-Modified-Apache-2.0Not stated
Repository (differs)github.com/zocks-communications/zocks-agent-pluginsgithub.com/layercall/layercall-sdk
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot 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

Zocks Advisor Intelligence

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

Seven skills for financial advisors built on Zocks meeting intelligence: client behavioral profiles, attrition-risk ranking, held-away asset radar, client journey dossiers, household review packs, next-best-action analysis and a tax opportunity scan. Requires the Zocks connector and a Zocks account.

LayerCall

In its own words, on Official MCP Registry:

Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.

How to run each

Zocks Advisor Intelligence As a Claude Code plugin

Claude Code
/plugin install zocks-advisor@claude-plugins-official

LayerCall As a remote MCP server

Claude Code
claude mcp add --transport http trust-api https://www.layercall.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Neither one's marketplaces publish the settings it asks for.

What it can do: Zocks Advisor Intelligence · What it can do: LayerCall · Compare two other plugins

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

Where the data comes from: how the catalog is built