Slvdev Weasel
- 26 repo stars
- Updated January 27, 2026
- slvDev/weasel
Weasel is a Claude Code plugin that connects a Solidity static analyzer over MCP so you can audit smart contracts conversationally in your coding agent.
About
Weasel is a Claude Code marketplace plugin that wraps a Solidity static analyzer behind MCP so you can talk to security findings instead of only reading CLI reports. developers shipping DeFi tools, NFT backends, or on-chain automation often lack a dedicated auditor; Weasel fits the gap between writing contracts in Build and proving they are safe enough to Ship. Connect it in Claude Code, Cursor, or Windsurf, point it at Solidity sources, and use natural-language follow-ups to understand severity and fix paths. It complements manual review and formal audits rather than replacing them—think continuous static analysis during implementation and pre-launch checks. The repo markets analysis, auditing, and secure development keywords explicitly, which aligns with Skillselion’s Ship and security facets for Web3 developers.
- Solidity-focused static analysis exposed as an MCP server
- Conversational auditing from Claude Code, Cursor, and Windsurf
- Security-category marketplace plugin for smart-contract development
- Emphasis on secure development and static-analysis workflows
- Single-plugin bundle from slvDev/weasel repository
Slvdev Weasel by the numbers
- Data as of Jul 18, 2026 (Skillselion catalog sync)
/plugin install slvdev-weasel@slvDev/weaselAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 26 |
|---|---|
| Last updated | January 27, 2026 |
| Repository | slvDev/weasel ↗ |
What it does
Install Weasel when you want a Solidity static analyzer you can query through MCP from Claude Code, Cursor, or Windsurf while hardening smart contracts.
Who is it for?
Best when you're writing Solidity and already use Claude Code or Cursor and want MCP-driven security checks before launch.
Skip if: Skip if you need formal third-party audit sign-off, non-EVM chains, or security review with zero smart-contract source access.
What you get
After MCP setup, you can query Weasel from Claude Code, Cursor, or Windsurf for static analysis and auditing guidance while iterating contracts toward safer deployment.
- MCP-accessible static analysis runs on Solidity code
- Agent-guided interpretation of audit and security findings
- Repeatable pre-ship security pass integrated into your IDE workflow
Recommended Plugins
1mangesh1 Hipaa GuardianAI agent skill for HIPAA compliance - PHI/PII detection, code scanning, audit reports, and remediation guidance6
Abossenbroek Abossenbroek Claude PluginsCustom Claude Code plugins by abossenbroek2
Agentsecops SecopsagentkitSecurity operations toolkit for AI coding agents.181
Agent Sh EnhancePlugin structure and tool use analyzer - validates plugin.json, MCP tools, and security patterns3
Altic Dev EnvaultLet agents safely manage env variables6
Auth0 Agent SkillsAuth0 Agent Skills40How it compares
MCP-backed Solidity static analyzer, not a general-purpose JavaScript linter or agent planning skill.
FAQ
Who is Slvdev Weasel for?
It is for developers building Solidity smart contracts who want static analysis and audit-style questions inside Claude Code, Cursor, or Windsurf via MCP.
When should I use Slvdev Weasel?
Use it during implementation and pre-ship hardening whenever you change contract logic and need fast static-analysis feedback before deployment.
How do I add Slvdev Weasel to my agent?
Install the slvDev/weasel plugin from the marketplace, configure the Weasel MCP server per the repo docs, then invoke analysis from Claude Code, Cursor, or Windsurf on your Solidity project.