auditsentry vs dev.weakspot/weakspot
auditsentry is a plugin bundle for AI coding tools published by Iktok Security Labs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). dev.weakspot/weakspot is an MCP server published by weakspot.dev. 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 | ||
|---|---|---|
| Community marketplace iktok90-design/ai-smart-contract-auditor | Listed Version: 1.0.0 Forks (GitHub): 6 Stars (GitHub): 37 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (npm): 144 Downloads/week (npm): 7 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 | auditsentry | dev.weakspot/weakspot |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 37 | No figure on GitHub |
| Forks (GitHub) (differs) | 6 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (weakspot-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 12, secrets among them: 5 | 4, secrets among them: 1 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 128 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/iktok90-design/ai-smart-contract-auditor | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
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
auditsentry
AI-powered smart contract security auditor for Claude Code — vuln detection, exploit PoCs, mainnet-fork sims, audit cards, on-chain certificates.
dev.weakspot/weakspot
Audit Solidity and Rust smart contracts from your editor. Pays per audit in USDC over x402.
How to run each
auditsentry As a Claude Code plugin
/plugin marketplace add iktok90-design/ai-smart-contract-auditor
/plugin install auditsentry@auditsentry
dev.weakspot/weakspot As a local MCP server: npm package
claude mcp add --env "WEAKSPOT_PRIVATE_KEY=<YOUR_WEAKSPOT_PRIVATE_KEY>" --transport stdio weakspot -- npx -y weakspot-mcp
Requires: WEAKSPOT_PRIVATE_KEY (secret)
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
Only auditsentry asks for
ARBISCAN_API_KEY (secret)BASESCAN_API_KEY (secret)BERATRAIL_API_KEY (secret)ECHIDNA_PATHETHERSCAN_API_KEY (secret)HALMOS_PATHMEDUSA_PATHMYTHRIL_PATHSLITHER_PATHTENDERLY_ACCESS_KEY (secret)TENDERLY_ACCOUNTTENDERLY_PROJECT
Only dev.weakspot/weakspot asks for
WEAKSPOT_MAX_USDWEAKSPOT_PRIVATE_KEY (secret)WEAKSPOT_RPC_URLWEAKSPOT_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: auditsentry · What it can do: dev.weakspot/weakspot · Compare two other plugins
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.