simulate — tech risk MCP Tool
simulate
(simulate) is one of 34 tools on the
tech risk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call simulate from your client
- Claude Code tech risk simulate run in your project directory
- Claude Desktop tech risk simulate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor tech risk simulate ~/.cursor/mcp.json
- VS Code tech risk simulate .vscode/mcp.json
- Zed tech risk simulate ~/.config/zed/settings.json
- Windsurf tech risk simulate ~/.codeium/windsurf/mcp_config.json
- Cline tech risk simulate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI tech risk simulate ~/.gemini/settings.json
- Grok tech risk simulate .mcp.json (in your project root)
- ChatGPT tech risk simulate Settings → Connectors → Advanced → Developer mode
- Claude.ai tech risk simulate Settings → Connectors → Add custom connector
- LangChain tech risk simulate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tech-risk https://x402-data-api.sigrunner.workers.dev/mcpOther tools on this server
- enrich_tech_risk
- enrich_domain
- scan_mcp_server
- scan_mcp_preview
- crypto_prices
- crypto_funding
- defi_yields
- yield_entry_verdict
- pm_markets
- crypto_prices_preview
- crypto_funding_preview
- defi_yields_preview
- yield_entry_verdict_preview
- simulate_preview
- pm_markets_preview
- chain_block_number
- chain_gas_price
- chain_balance
- chain_token_balance
- chain_tx
- chain_wallet
- chain_wallet_screen
- x402_preflight
- x402_receipt_verify
- x402_receipt_verify_preview
- chain_token_security
- chain_block_number_preview
- chain_gas_price_preview
- chain_token_report
- gate_swap
- gate_swap_preview
- chain_token_report_preview
- chain_token_security_preview
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.