Slvdev Weasel
Weasel is a Claude Code plugin for the Ship phase that connects a Solidity static analyzer over MCP so you can audit smart contracts conversationally in your coding agent.
by slvDev · github.com/slvDev/weasel
Install Weasel when you want a Solidity static analyzer you can query through MCP from Claude Code, Cursor, or Windsurf while hardening smart contracts.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install slvdev-weasel@slvDev/weaselBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:slvDev/weasel") and the paste-ready config with skillselion.get_install_config("plugin:slvDev/weasel").
What it does
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. Solo builders 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 indie Web3 builders.
Highlights
- 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
Why builders use it
Indie Solidity developers struggle to catch vulnerability patterns early because traditional static-analysis output is noisy and disconnected from the agent where they actually edit code.
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.
At a glance
- Type - Plugin in Security.
- Adoption - 0 installs, 26 stars, 0 votes.
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.
Comments
Share how you use slvdev-weasel, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.