acuris vs Limitguard Lead Verification
acuris is a plugin bundle for AI coding tools published by Acuris-GmbH. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Limitguard Lead Verification is an MCP server published by api.limitguard.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  acuris |   Limitguard Lead Verification |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 5fb6ebe Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.11.9 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 | acuris | Limitguard Lead Verification |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.limitguard.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/acuris-gmbh/acuris-agent-context | github.com/jwconsultancyteam/limitguard-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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
acuris
Two model-invoked skills for the Acuris APIs. `acuris-address` teaches the Acuris Address Validation & Geocoding SDK (`@acuris-geo/av-sdk`) — validate, geocode, reverse, autocomplete — plus React component recipes for Next.js, Centra, commercetools, and SCAYLE storefronts, plus migration recipes from libAddressDoctor (Informatica), Loqate, Experian QAS, Melissa, and Smarty. `acuris-eudi` teaches relying-party integration with the Acuris EUDI Wallet Verifier (OID4VP / SD-JWT VC at eudi.acuris-geo.com), covering session lifecycle, polling, and trust validation across EU 27 member-state TSLs. Each skill auto-activates only when your task mentions its area, so installing both costs almost no context.
Limitguard Lead Verification
Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.
How to run each
acuris As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install acuris@claude-communityLimitguard Lead Verification As a remote MCP server
claude mcp add --transport http limitguard https://api.limitguard.ai/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.
Only Limitguard Lead Verification 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: acuris · What it can do: Limitguard Lead Verification · 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.