概览
What is MCP Ethereum Address Info Server?
The server provides information about Ethereum addresses across multiple chains using the Model Context Protocol (MCP). It includes a Server-Sent Events (SSE) endpoint for real-time updates, making it suitable for developers needing live address monitoring and data retrieval.
How to use MCP Ethereum Address Info Server?
Clone the repository, run npm install, and create a .env file with MCP_PORT=3002 (default port is 3002). Start with npm run start:http. Use curl to call endpoints: connect to /sse, subscribe to addresses via /sse/subscribe/:clientId, and trigger updates using the get-address-info tool via /mcp.
Key features of MCP Ethereum Address Info Server
- Provides Ethereum address info across multiple chains
- Real-time updates via Server-Sent Events (SSE) endpoint
- Subscribe and unsubscribe to specific address updates
- HTTP MCP endpoint for tool calls (
get-address-info,ping) - Health check endpoint (
GET /health) - Client management endpoint (
GET /sse/clients)
Use cases of MCP Ethereum Address Info Server
- Monitor Ethereum addresses in real time across chains
- Retrieve address information programmatically via MCP tools
- Build dashboards or alerting systems that react to address updates
- Test and debug SSE subscriptions with provided curl examples and automation scripts
FAQ from MCP Ethereum Address Info Server
What data does the server return for an Ethereum address?
The server returns information about Ethereum addresses. The README does not specify the exact data fields returned.
How do I set up the server?
Clone the repo, run npm install, create a .env file with MCP_PORT (default 3002), and start with npm run start:http.
How do I receive real-time address updates?
Connect to the /sse endpoint with curl -N http://localhost:3002/sse, obtain your client ID, subscribe to addresses via /sse/subscribe/:clientId, and trigger updates by calling the get-address-info tool.
What are the runtime dependencies?
Node.js and npm. The README does not list specific version requirements.
How do I test the server without a full client?
Use the provided curl commands for all endpoints, or run the automated bash script (test_sse.sh) included in the README.
