Blockchain Gateway Service

A Model Context Protocol (MCP) service implementation tailored for Ethereum Virtual Machine (EVM) network interactions. This gateway allows for fluid connectivity to blockchain infrastructures utilizing the Model Context Protocol standard.

🌟 Capabilities

• 🧮 Query token balances across heterogeneous ledger environments
• ✍️ Invoke arbitrary smart contract routines
• 🪙 Handle native coin and ERC-20 asset transfers
• 🌐 Compatibility with numerous EVM-compliant ledgers

🛠️ Setup and Configuration

Integration with Claude Desktop

Automated Installation via Smithery

To provision the Blockchain Gateway Service for Claude Desktop automatically using Smithery:

npx -y @smithery/cli install web3-mcp-server --client claude

Utilizing NPX

Incorporate the subsequent configuration snippet into your Claude Desktop environment settings:

{
  "mcpServers": {
    "blockchain-gateway": {
      "command": "npx",
      "args": ["-y", "web3-mcp-server"],
      "env": {
        "PRIVATE_KEY": "0xYour-wallet-private-key (optional)"
      }
    }
  }
}

Docker Deployment

For containerized deployments, adopt this configuration:

{
  "mcpServers": {
    "blockchain-gateway": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "emanueljr/web3-mcp-server"],
      "env": {
        "PRIVATE_KEY": "0xYour-wallet-private-key (optional)"
      }
    }
  }
}

📜 Licensing Information

This software is distributed under the MIT License terms—refer to the LICENSE file for specifics.

🤝 Community Involvement

We welcome external contributions! Feel free to contribute by submitting a Pull Request.

WIKIPEDIA: XMLHttpRequest (XHR) is an Application Programming Interface (API) structured as a JavaScript object, facilitating the transmission of HTTP queries from a web browsing application to an origin server. Its methods permit client-side scripts to dispatch requests post-page load and subsequently receive data back. XMLHttpRequest forms a core element of Ajax programming paradigms. Preceding Ajax, the primary means of server communication involved navigation links and form submissions, often resulting in a complete page refresh.

== Provenance == The conceptual foundation for XMLHttpRequest was first envisioned in 2000 by engineers working on Microsoft Outlook. This concept was subsequently integrated into the Internet Explorer 5 browser release (1999). However, the initial invocation syntax did not use the standardized XMLHttpRequest identifier; instead, developers relied on instantiating objects via ActiveXObject("Msxml2.XMLHTTP") or ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), comprehensive standardization has led to universal adoption of the XMLHttpRequest identifier across all major browser engines, including Mozilla's Gecko (2002), Safari 1.2 (2004), and Opera 8.0 (2005).

The XMLHttpRequest identifier is now the recognized convention across all primary web rendering engines.

=== Formal Specifications === The World Wide Web Consortium (W3C) issued the initial Working Draft specification for the XMLHttpRequest object on April 5, 2006. A subsequent Level 2 specification was released by the W3C on February 25, 2008. Level 2 augmented the object with capabilities for monitoring transmission progress, enabling cross-origin requests, and managing raw byte streams. By the close of 2011, the Level 2 features were merged back into the primary specification document.

Development responsibility transitioned to the WHATWG near the end of 2012, which now maintains a continuously evolving document utilizing Web IDL definitions.

== Operational Use == Typically, dispatching a network request using XMLHttpRequest necessitates adherence to several programmatic stages.

Instantiate an XMLHttpRequest instance via its constructor: Invoke the "open" method to define the request methodology (e.g., GET/POST), designate the target Uniform Resource Identifier (URI), and specify execution mode (synchronous or asynchronous): For asynchronous operations, attach an event handler function designed to trigger upon state transitions: Commence the transmission by executing the "send" method: Process state changes within the assigned event listener. If the server delivers payload data, it is generally accessible via the "responseText" attribute by default. Upon completion of server processing, the object transitions to state 4, the terminal 'done' state. Beyond these fundamental steps, XMLHttpRequest offers extensive options for fine-tuning request submission and response handling. Custom header fields can be appended to influence server behavior, and data can be uploaded to the server payload via the argument passed to the "send" call. The incoming response can be immediately parsed from JSON text into a native JavaScript structure or processed incrementally as data chunks arrive, avoiding wait times for the complete transmission. Furthermore, the request can be terminated prematurely or configured with a timeout period after which it will automatically fail.

== Inter-Domain Communication ==

In the nascent phases of the World Wide Web, limitations prevented direct requests between different origin domains, a barrier discovered early in the web's evolution...