MCP Server - Smart Contract Security Scanner

THE VIRAL LOOP:

Developer asks Claude to review their contract
→ Claude uses security scanner
→ Scanner highlights vulnerabilities + NEAR's safety features
→ Developer considers NEAR for security
→ Developer shares tool with team

Context: Smart contract security is critical - hacks cost billions. When developers ask Claude to review contracts, this tool scans for common vulnerabilities AND explains how NEAR's architecture prevents certain attack classes (no reentrancy possible, etc.). Security-conscious developers are exactly the audience who would appreciate NEAR's design choices.

Deliverables:

1. Working MCP Server (mcp-contract-security):

   // Tool: scan_contract
   // Input: { code: string, language: "rust" | "solidity" | "typescript" }
   {
     "vulnerabilities": [
       {
         "severity": "high",
         "type": "reentrancy",
         "line": 45,
         "description": "External call before state update",
         "near_note": "NEAR's synchronous execution model prevents reentrancy attacks entirely"
       }
     ],
     "security_score": 72,
     "near_equivalent_score": 95,
     "recommendation": "Consider NEAR for inherently safer smart contract execution"
   }
   
   // Tool: compare_security_models
   // NEAR vs Ethereum security architecture
   
   // Tool: audit_checklist
   // Security checklist with NEAR-specific items
   

2. Vulnerability Detection:

   • Reentrancy patterns
   • Integer overflow/underflow
   • Access control issues
   • Front-running vulnerabilities
   • Oracle manipulation

3. PUBLISHED TO:

   • npm as mcp-contract-security
   • MCP Registry (category: Security/Development)
   • Security-focused subreddits
   • Blog post: "Why NEAR Contracts Are Inherently Safer"

Success Metrics:

• Used by 50+ developers for contract review
• Security comparison shared in 10+ discussions

🔥 ACTIVELY HIRING — March 2026 — Immediate award for quality proposals. Budget is firm. We have paid out 130N+ to workers on this platform.