mcp-contract-security
Provides smart contract security scanning for NEAR, including vulnerability detection and NEAR-specific security notes and recommendations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-contract-security scan this Solidity contract for vulnerabilities and give me a security score"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-contract-security
MCP server for smart contract security scanning.
Implements the required tools:
scan_contractcompare_security_modelsaudit_checklist
Supports languages:
solidityrusttypescript
What it checks
scan_contract currently detects heuristic patterns for:
Reentrancy
Integer overflow/underflow risk
Access control issues
Front-running exposure
Oracle manipulation risk
The output includes:
vulnerability list with severity/type/line
security_scorenear_equivalent_scoreNEAR-specific security notes and recommendation
Related MCP server: meok-mcp-injection-scan-mcp
Install
npm install -g mcp-contract-securityPublished package:
MCP Registry: https://registry.modelcontextprotocol.io/v0/servers/io.github.mastrophot%2Fcontract-security-scanner/versions/0.1.1
MCP config (Claude Desktop)
{
"mcpServers": {
"contract-security": {
"command": "mcp-contract-security"
}
}
}Tool usage
scan_contract
Input:
{
"code": "contract source code here",
"language": "solidity"
}compare_security_models
Input (optional):
{
"language": "solidity"
}audit_checklist
Input (optional):
{
"language": "rust"
}Local development
npm install
npm run checkDeliverable assets
Additional publish assets are prepared in deliverables/:
deliverables/mcp-registry-submission.mddeliverables/security-subreddit-posts.mddeliverables/blog-why-near-contracts-safer.mdserver.json(MCP Registry metadata, schema-validated)
License
MIT
Available Tools
3 toolsaudit_checklistB
Return a practical smart contract security checklist with NEAR-specific items.
Inputs: language.
compare_security_modelsB
Compare NEAR vs Ethereum security architecture and risk profile.
Inputs: language.
scan_contractB
Scan contract code for common vulnerabilities and include NEAR-specific security notes.
Inputs: code (required), language (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: scanning contracts for vulnerabilities, comparing architectures, and providing checklists. There is no meaningful overlap that would cause an agent to select the wrong tool.
Two tools follow a verb_noun pattern (scan_contract, compare_security_models), while audit_checklist is more of a noun phrase. The pattern is mostly predictable and readable, with only a minor deviation.
Three tools is a reasonable scope for a focused contract security server. It is slightly small but each tool serves a distinct, justified function within the domain.
The toolset covers scanning, comparative analysis, and actionable guidance, which gives agents a solid workflow. It lacks deeper features like detailed report generation or code fixes, but the core security assessment use case is well covered.
Maintenance
Related MCP Connectors
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Scans an MCP server for security gaps before your agent connects. Free tier, no signup.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceSecurity scanner for MCP servers. Detects prompt injection, command injection, auth bypass, and excessive permissions across tools, resources, and prompts.24 npm3MIT
- AlicenseAqualityDmaintenanceScans MCP servers for prompt-injection, tool-poisoning, and SSRF vulnerabilities using 30+ canonical rules across 5 severity tiers, with optional signed safety reports for procurement.5MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that statically audits Solidity smart contracts for common vulnerabilities like reentrancy and access control, enabling developers to identify and fix security issues via natural language.-
- AlicenseNot gradedqualityDmaintenanceEnables scanning Solidity smart contracts for 13 vulnerability classes using pattern-based analysis; provides full audit, quick scan, gas analysis, and detector catalog through MCP tools.MIT