Provides universal JSON-RPC communication with any EVM-compatible blockchain network, enabling direct querying of balances, transactions, blocks, and contract data across multiple blockchain networks including specialized chain functions like Zircuit's quarantine system.
Chain Debugger MCP Server
An integrated MCP (Model Context Protocol) server providing dual blockchain connectivity:
- Tenderly Integration: Comprehensive read-only access to Tenderly's monitoring infrastructure and alerting systems
- Universal EVM RPC Support: Native JSON-RPC communication with any EVM-compatible blockchain network
Built to bridge AI assistants with blockchain ecosystems, enabling seamless monitoring through Tenderly while maintaining direct chain interaction capabilities via standardized protocols.
Overview
This MCP server establishes a robust connection between AI systems and blockchain infrastructure via the Model Context Protocol. The server empowers AI assistants like Claude with comprehensive blockchain capabilities:
Tenderly Integration:
- Complete alert management - Full access to all project alerts with detailed metadata
- Granular alert inspection - Deep-dive into specific alerts by ID with comprehensive details
- Advanced monitoring analytics - Process blockchain monitoring data for actionable insights
- Transaction simulation engine - Leverage Tenderly's sophisticated simulation capabilities
EVM RPC Capabilities:
- Universal JSON-RPC execution - Run any standard or custom RPC method across EVM networks
- Direct blockchain querying - Access balances, transactions, blocks, and contract data natively
- Multi-chain architecture - Configurable endpoints supporting diverse EVM-compatible networks
- Specialized chain functions - Enhanced features for specific networks (Zircuit quarantine system, etc.)
Core Architecture Features
- 🔒 Non-invasive design - Exclusively retrieval-based operations with zero modification capabilities
- 🚀 Plug-and-play compatibility - Seamless integration with any MCP-compliant AI assistant
- 📊 Comprehensive alert intelligence - Full access to alert expressions, delivery configurations, severity classifications, and metadata
- 🛡️ Enterprise-grade type safety - Complete TypeScript implementation with comprehensive Zod schema validation
- 🔐 Security-first credential handling - Environment-based secret management with zero hardcoded credentials
Prerequisites
- Node.js v16+ runtime environment
- Active Tenderly account with API privileges
- Tenderly authentication credentials (account slug, project identifier, access token)
- Optional: EVM RPC endpoint URL for direct blockchain connectivity
Installation & Configuration
- Clone the repository to your local environment
- Install all required dependencies:
- Initialize your environment configuration:
- Configure your
.env
file with the following parameters: - Compile the TypeScript project:
Usage
Server Execution
Launch the MCP server:
The server operates through stdio (standard input/output) communication following MCP specification standards. Initialization logs output to stderr while the server awaits MCP protocol messages via stdin.
For dynamic EVM RPC configuration, command-line arguments are supported:
AI Assistant Integration
Once operational, AI assistants gain access to your Tenderly infrastructure through the following capabilities:
Resource Endpoints:
tenderly://alerts
- Complete JSON enumeration of all project alerts with metadatatenderly://simulations
- Direct access to Tenderly's transaction simulation infrastructureevm://rpc_info
- Current EVM RPC connection status and configuration detailsevm://chain_info
- Network identification and chain-specific metadata
Functional Tools:
get_alert_by_id(id: string)
- Detailed alert retrieval with comprehensive metadatasimulate_transaction(...)
- Advanced transaction simulation via Tenderly's engineeth_json_rpc_call(method, params)
- Universal Ethereum JSON-RPC method executionzirc_isQuarantined(transactionHash)
- Zircuit-specific transaction quarantine status checkingzirc_getQuarantined(address?)
- Quarantined transaction enumeration for Zircuit network
Practical Use Cases
With the server connected to an AI assistant, you can perform queries such as:
Tenderly Operations:
- "Enumerate all alerts configured in my Tenderly project"
- "Provide comprehensive details for alert ID abc123"
- "Identify which alerts are currently active and operational"
- "Analyze the most critical alerts requiring immediate attention"
- "Execute a simulation for a 1 ETH transfer between specified addresses"
EVM RPC Operations:
- "Retrieve the current blockchain height"
- "Query ETH balance for address 0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
- "Fetch transaction receipt for hash 0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060"
- "Extract bytecode from the USDC contract address"
- "Verify quarantine status for transaction 0xabc..." (Zircuit-specific)
The AI assistant leverages this server to retrieve blockchain data and deliver sophisticated analysis of your on-chain activities.
Development & Testing
The MCP Inspector provides comprehensive server testing capabilities:
This launches a web-based interface enabling direct testing of all MCP resources and tools.
Technical Architecture
MCP Resource & Tool Implementation
Resource Infrastructure:
tenderly://alerts
- Comprehensive alert enumeration from your Tenderly project, including:- Complete alert metadata (IDs, names, descriptions)
- Operational status indicators (enabled/disabled states)
- Alert expression logic and trigger conditions
- Delivery channel configurations and routing
- Severity classification and visual coding
- Temporal metadata (creation and modification timestamps)
Tool Framework:
get_alert(id: string)
- Granular alert data retrieval with complete metadata extraction
Data Structure Design
The server returns structured alert data containing:
- Core Attributes: Unique identifiers, names, descriptions, operational status
- Logic Components: Trigger expressions, conditional logic, evaluation criteria
- Distribution Configuration: Delivery mechanisms, routing destinations, notification channels
- System Metadata: Project associations, temporal markers, severity indicators, visual classifications
- Access Control: API token permissions and modification privileges
System Architecture
The server operates as a secure intermediary proxy, handling MCP request translation to Tenderly API calls while ensuring response formatting adheres to MCP specification requirements.
Configuration Constraints
The current implementation operates within these architectural boundaries:
- Environment Configuration: Single
.env
file support per instance. Multi-environment configurations require separate.env
files or command-line parameter overrides for different deployment scenarios. - Network Connectivity: One EVM RPC endpoint per server instance. Multi-chain simultaneous connections require separate server instances, though future architectural enhancements will address this limitation.
- Memory Store Configuration: Single memory store configuration (
ENABLE_MEMORY
andMEMORY_STORE_PATH
) per instance. Multiple memory backends are not currently supported within a single process. - Analytics Configuration: One analytics configuration set (
ENABLE_ANALYTICS
andANALYTICS_DB_PATH
) per server instance.
For diverse configuration requirements across these features, deploy multiple server instances with distinct configuration profiles or command-line parameter sets.
Security Assessment & Verification
✅ COMPREHENSIVE SECURITY VALIDATION COMPLETED
Security Analysis Results
A thorough security evaluation of this codebase reveals the following validated findings:
✅ Dependency Security Clearance
npm audit
confirms zero vulnerabilities across all dependencies- All dependencies sourced from established, well-maintained repositories
- No known CVE exposures affecting this project's dependency chain
✅ Non-Destructive Operation Model
- Exclusively data retrieval operations - zero modification capabilities
- No write operations to blockchain networks, databases, or file systems
- Transaction execution and state mutation are architecturally impossible
✅ Secure Communication Standards
- Exclusive connections to official Tenderly API (
api.tenderly.co
) via HTTPS - Zero connections to unverified or potentially malicious endpoints
- All API communications properly authenticated using provided tokens
✅ Secure Credential Architecture
- Credentials exclusively managed through
.env
files (version control excluded) - Zero hardcoded secrets or API keys within source code
- Comprehensive environment variable validation prior to utilization
✅ Enterprise Code Quality Standards
- Complete TypeScript implementation with strict typing enforcement
- Comprehensive Zod validation for all API responses preventing injection vulnerabilities
- Clean, maintainable code architecture with robust error handling
- Complete absence of eval(), exec(), or other potentially dangerous functions
✅ Minimal Privilege Requirements
- Operates with standard user permissions - no elevated privileges required
- File system modifications strictly limited to project directory scope
- Zero system-level operations or administrative access requirements
Dependency Trust Verification
@modelcontextprotocol/sdk
- Official MCP SDK maintained by Anthropicdotenv
- Industry-standard, extensively audited environment variable managementzod
- TypeScript-native schema validation library with proven security record
Security Risk Classification: MINIMAL
This implementation represents a straightforward, secure API client with zero identified security risks when deployed with proper configuration.
Tenderly Credential Setup
Server operation requires valid Tenderly API credentials:
- Account Registration - Establish a Tenderly account
- Project Initialization - Create a new project or utilize an existing project
- API Token Generation:
- Navigate to Account Settings
- Select "Create API Key"
- Securely copy your generated access token
- Credential Identification - Extract your account slug and project ID from the Tenderly dashboard URL:
- URL Format:
https://dashboard.tenderly.co/{account-slug}/{project-id}/...
- URL Format:
Contributing
Contributions to this project are welcome! Please ensure all changes preserve the established security standards and maintain the implementation's architectural simplicity.
License
MIT
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Enables AI assistants to monitor and analyze blockchain activity through Tenderly's infrastructure and direct EVM RPC calls. Provides comprehensive alert management, transaction simulation, and multi-chain querying capabilities for blockchain debugging and monitoring.
Related MCP Servers
- -securityAlicense-qualityA secure system enabling AI assistants to interact with blockchain data and prepare transactions while ensuring users maintain exclusive control over their private keys and transaction signing.Last updated -9MIT License
- AsecurityAlicenseAqualityProvides tools for AI assistants to interact with the Ethereum blockchain through standard JSON-RPC methods, enabling queries for account balances, gas prices, and smart contract code.Last updated -39MIT License
- AsecurityAlicenseAqualityA comprehensive server that enables AI agents to interact with multiple EVM-compatible blockchain networks through a unified interface, supporting ENS resolution, token operations, and smart contract interactions.Last updated -282,922MIT License
- -securityAlicense-qualityA powerful toolkit that enables seamless interaction with EVM-compatible networks through natural language processing and AI assistance, allowing users to manage wallets, launch tokens, and interact with blockchain networks.Last updated -6MIT License