fluidityiq-patent-intelligence vs ActTrace
fluidityiq-patent-intelligence is a plugin bundle for AI coding tools published by FluidityIQ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ActTrace is an MCP server published by goww7. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 |  fluidityiq-patent-intelligence |  ActTrace |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.4.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (PyPI): 95 Downloads/week (PyPI): 29 Forks (GitHub): 0 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
| Fact | fluidityiq-patent-intelligence | ActTrace |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (patents.fluidityiq.ai/mcp) | On your machine (acttrace-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/fluidityiq/patent-intelligence-plugin | github.com/goww7/acttrace |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no 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
fluidityiq-patent-intelligence
Patent Intelligence automates patentability assessments for IP teams. It connects to the FluidityIQ Patents MCP to perform semantic prior art searches across global patent databases, classify references by threat level (anticipatory, combinable, or background), build feature-to-prior-art coverage matrices with specific citations, and generate structured Patentability Assessment Reports with novelty and non-obviousness analysis. Designed for patent counsel, patent agents, inventors, and IP portfolio managers.
ActTrace
Classify AI systems under the EU AI Act and generate Article 50 transparency notices.
How to run each
fluidityiq-patent-intelligence As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install fluidityiq-patent-intelligence@claude-communityActTrace As a local MCP server: PyPI package
claude mcp add --transport stdio acttrace -- uvx acttrace-mcpCommands 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: fluidityiq-patent-intelligence · What it can do: ActTrace · 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 the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.