mcp-kritisi
Related Servers
Alternatives to mcp-kritisi
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables static analysis, vulnerability scanning, gas optimization, formal specification verification, and audit report generation for smart contracts across Ethereum, Polygon, Arbitrum, Optimism, and Base. It also retrieves deployed contract information and audit history, persisting findings between sessions.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables automated Solidity smart contract auditing by analyzing callgraphs and control flow to detect reentrancy vulnerabilities. Integrates with MCP-compatible clients to provide deterministic, zero-dependency security assessments.-
- AlicenseNot gradedqualityCmaintenanceEnables smart contract security auditing using Slither, Aderyn, and custom pattern analysis through the Model Context Protocol, allowing AI assistants to run static analysis and vulnerability checks on Solidity and Vyper contracts.1Apache 2.0

Slither MCP Serverofficial
AlicenseAqualityDmaintenanceEnables static analysis of Solidity smart contracts using Slither, including contract metadata, function details, inheritance, and security detectors through MCP tools.2399AGPL 3.0- FlicenseNot gradedqualityNot gradedmaintenanceEnables auditing EIP-712 typed signature phishing permits and sanitizing allowances (Permit2/MetaMask) via MCP, with deterministic callgraph verification and DeFi vulnerability triage. It integrates with Claude Desktop, Cursor, and MCP clients for autonomous smart contract security analysis.-
- AlicenseBqualityBmaintenanceCommit-time audit engine for AI coding agents. Scans git diffs with 24 audit rules, writes HMAC-signed tamper-evident audit history, and ships MCP tools for governance aggregation.10456MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: showing configuration, security auditing, NatSpec documentation, and import merging. There is no meaningful overlap between tool behaviors or target outputs.
All names use consistent snake_case with two-word identifiers, making the set easy to scan. The verb/noun convention is mostly predictable, though security_audit and natspec_document are more noun-oriented than the action-first names.
Four tools is appropriately small for a focused Solidity utility wrapper. Each tool maps to a distinct workflow and none feels redundant or ornamental.
The surface covers configuration visibility, auditing, documentation generation, and import merging, which are the core operations implied by the server. Minor gaps exist around broader Solidity workflows, but the stated purpose is well served.