Ext Ops Panel
Open dashboard
Comparison

slice-global vs Intangible Asset Valuation MCP Server

slice-global is a plugin bundle for AI coding tools published by Global-Slice. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Intangible Asset Valuation MCP Server is an MCP server published by ascent-partners.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplaceslice-globalIntangible Asset Valuation MCP Server
Claude Code: claude-plugins-community Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.4
Forks (GitHub): 1
Stars (GitHub): 1
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

slice-global vs Intangible Asset Valuation MCP Server
Factslice-globalIntangible Asset Valuation MCP Server
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)9 (better)1 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.app.sliceglobal.com)Remote server (intangible-valuation.ascent-partners.com/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/global-slice/claude-plugingithub.com/simonmak-ascent/intangible-valuation
Changes in the last 7 days (differs)25
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 10 h ago, requires a keyResponded 46 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

slice-global

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

Official Slice plugin for Claude. Ask Claude about your cap table, grants, share classes, ESOP pools, compliance posture, valuations, workflows, and exit waterfalls - all through the read-only Slice MCP server, scoped to your Slice login via OAuth, with tokens stored only on your machine.

Intangible Asset Valuation MCP Server

In its own words, on Official MCP Registry:

Intangible asset valuation: 14 tools, 124+ formulas for IP, technology, goodwill, PPA, impairment.

How to run each

slice-global As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install slice-global@claude-community

Intangible Asset Valuation MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http intangible-valuation https://intangible-valuation.ascent-partners.com/api/mcp

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of slice-global nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: slice-global · What it can do: Intangible Asset Valuation MCP Server · 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 public marketplace files in GitHub repositories of their authors. 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