solidity-lint vs dev.weakspot/weakspot
solidity-lint is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
solidity-lint is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. 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-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  dev.weakspot/weakspot | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | solidity-lintno longer listed · | dev.weakspot/weakspot |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (weakspot-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of solidity-lint
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Script-backed, out-of-box auditing workflow for Solidity/EVM repositories. Covers environment bootstrap, vulnerability detection, patch validation, exploit scaffolding, and…
-
solidity
Production-grade Solidity development standards covering code quality, testing patterns, security practices, and Foundry workflows
-
Browser Solidity compiler IDE - smart contract development testing deploy
-
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
-
A friendly truffle pig that sniffs out design principle violations - Law of Demeter, SOLID, DRY, KISS, YAGNI and more.
-
contract-scanner io.github.lordbasilaiassistant-sudo/contract-scanner
Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding
What each says it does
solidity-lint
Generate Solidity linting and style configs
dev.weakspot/weakspot
Audit Solidity and Rust smart contracts from your editor. Pays per audit in USDC over x402.
How to run each
solidity-lint
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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-mcpRequires: 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
The marketplaces of solidity-lint publish no settings it asks for, so we do not compare settings.
What it can do: solidity-lint · 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.