Yultrace Audit
Run agent-driven EVM smart-contract audits combining Slither, on-chain source, security.txt, MCP probes, and wallet-exposure checks before mainnet deploy.
Overview
Yultrace Audit is an MCP server for the Ship phase that orchestrates EVM smart-contract audits with Slither, source checks, security.txt, MCP probes, and wallet-exposure tooling.
What is this MCP server?
- Six MCP tools plus a dedicated /trace path for audit workflows
- Slither static analysis wired into agent-callable steps
- security.txt and source verification in one surface
- MCP-probe and wallet-exposure checks for live contract risk
- Streamable HTTP remote at trycloudflare-hosted endpoint (v0.1.6)
- 6 MCP audit tools plus /trace
- Server version 0.1.6
- Streamable HTTP remote MCP transport
What problem does it solve?
Indie Web3 builders stitch Slither, explorers, and ad-hoc scripts together because no single agent surface runs a coherent pre-launch contract audit.
Who is it for?
Solo builders hardening a contract repo with an AI coding agent and wanting Slither-plus-exposure checks in one MCP session.
Skip if: Teams that only need generic REST APIs or non-EVM security scanning without MCP or agent workflows.
What do I get? / Deliverables
Your agent can run a multi-step EVM audit pipeline from one MCP registration and capture traceable results before you ship or list bounties.
- Agent-invokable audit steps across six tools and /trace
- Consolidated view of Slither, source, security.txt, probe, and exposure signals
Recommended MCP Servers
Journey fit
How it compares
Specialized EVM audit MCP integration, not a general-purpose agent skill or marketplace catalog.
Common Questions / FAQ
Who is Yultrace Audit for?
EVM developers and security-minded solo builders who use Claude Code, Cursor, or similar agents to review contracts before launch.
When should I use Yultrace Audit?
During ship-phase security work when you need Slither, source, security.txt, probes, and wallet exposure in one agent-driven pass.
How do I add Yultrace Audit to my agent?
Register the streamable HTTP remote URL from the server manifest in your agent’s MCP settings and ensure your environment can reach the hosted endpoint.