Skip to main content
Glama
enesjakozh
zhangzhongnan928

MCP Blockchain Server

by zhangzhongnan928
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Servidor blockchain y DApp MCP

Un sistema seguro que permite a los asistentes de IA interactuar con contratos inteligentes de blockchain y al mismo tiempo garantizar que los usuarios mantengan un control total sobre sus claves privadas y la firma de transacciones.

Descripción general

Este proyecto aborda un desafío clave en la integración de IA y blockchain: permitir que los asistentes de IA lean datos de blockchain y preparen transacciones mientras se garantiza que los usuarios mantengan control exclusivo sobre la firma de transacciones y las claves privadas.

El sistema consta de:

  1. Servidor MCP : un servidor de protocolo de contexto de modelo que expone las operaciones de blockchain como herramientas que pueden ser utilizadas por asistentes de IA

  2. Web DApp : una aplicación React que proporciona una interfaz de usuario para la conexión de billetera y la firma de transacciones.

  3. Base de datos : base de datos PostgreSQL para almacenar usuarios, claves API y registros de transacciones

  4. Almacenamiento en caché : Redis para almacenar en caché datos a los que se accede con frecuencia

Related MCP server: ows-mcp-wallet

Características

Características del servidor MCP

  • Acceso a datos de blockchain : lectura de saldos, estado de contratos y otros datos en cadena

  • Preparación de transacciones : crear transacciones sin firmar para la aprobación del usuario

  • Compatibilidad con múltiples cadenas : funciona con Ethereum, Polygon y otras cadenas compatibles con EVM

  • Interacción de contratos inteligentes : lea contratos inteligentes verificados en redes compatibles

  • Diseño que prioriza la seguridad : las claves privadas nunca salen de la billetera del usuario

Características de la aplicación web DApp

  • Integración de billetera : conéctese con MetaMask y otras billeteras Web3

  • Revisión de transacciones : interfaz de usuario clara para revisar los detalles de la transacción antes de firmar

  • Firma de transacciones : Firme transacciones con la billetera conectada

  • Seguimiento de transacciones : supervise el estado de las transacciones enviadas

  • Compatibilidad móvil : el diseño adaptable funciona en todos los dispositivos.

Principios de seguridad

  1. Aislamiento de clave privada : las claves nunca salen de la billetera del usuario

  2. Verificación de transacciones : interfaz de usuario clara para revisar los detalles de la transacción

  3. Autenticación de API : gestión segura de claves API

  4. Limitación de velocidad : evitar el abuso

  5. Validación de entrada : desinfectar todas las entradas

  6. Registro de auditoría : seguimiento de todas las operaciones

  7. Sólo HTTPS : Comunicaciones seguras

  8. Política de seguridad de contenido : Prevenir XSS

Flujo de transacciones

  1. El asistente de IA solicita transacciones a través del servidor MCP

  2. El servidor MCP prepara una transacción sin firmar con UUID

  3. El servidor MCP devuelve la URL de la transacción al asistente de IA

  4. El asistente de IA proporciona la URL al usuario

  5. El usuario abre la URL en el navegador

  6. El usuario conecta la billetera y revisa los detalles de la transacción.

  7. El usuario aprueba y firma la transacción con su billetera

  8. La aplicación web DApp envía la transacción firmada a la cadena de bloques

  9. El estado de la transacción se actualiza y se rastrea.

Empezando

Prerrequisitos

  • Node.js (v18 o superior)

  • npm o hilo

  • PostgreSQL

  • Redis (opcional, para almacenamiento en caché)

  • Clave API de Infura (para acceso a blockchain)

  • Clave API de Etherscan (para ABI de contrato)

Instalación

  1. Clonar el repositorio:

git clone https://github.com/zhangzhongnan928/mcp-blockchain-server.git
cd mcp-blockchain-server

  1. Instalar dependencias:

npm install
# or
yarn install

  1. Configurar variables de entorno: Cree un archivo .env en el directorio raíz (o cópielo desde .env.example ):

cp .env.example .env
# Edit .env with your configurations

  1. Configurar la base de datos:

# For detailed instructions, see the Database Setup Guide
# docs/database-setup.md

# Create the PostgreSQL database
createdb mcp_blockchain

# Run database migrations
npm run db:migrate
# or
yarn db:migrate

Consulte la Guía de configuración de la base de datos para obtener instrucciones detalladas sobre la instalación y configuración de PostgreSQL.

  1. Iniciar el servidor:

npm run dev
# or
yarn dev

Uso de Docker Compose

Para comenzar rápidamente a utilizar Docker:

# Create .env file with required environment variables
cp .env.example .env
# Edit .env with your configurations

# Start the services
docker-compose up -d

Esto comenzará:

  • Base de datos PostgreSQL

  • Caché de Redis

  • Servidor MCP

  • Aplicación web descentralizada

Desarrollo

Estructura del servidor

  • src/mcp : Implementación del servidor MCP

  • src/services : Servicios de lógica empresarial básica

  • src/utils : Funciones de utilidad

  • src/index.ts : Punto de entrada principal

Estructura de la aplicación web DApp

  • web/src/components : Componentes de React

  • web/src/hooks : Ganchos de React personalizados

  • web/src/services : Servicios API

  • web/src/pages : Componentes de la página

Uso del servidor MCP

El servidor MCP expone varias herramientas que pueden utilizar los asistentes de IA:

  • get-chains : Obtener la lista de redes blockchain compatibles

  • get-balance : Obtener el saldo de la cuenta de una dirección

  • read-contract : Leer datos de un contrato inteligente

  • prepare-transaction : prepara una transacción sin firmar para la aprobación del usuario

  • get-transaction-status : obtener el estado actual de una transacción

Ejemplo de uso de la herramienta

// Example of using the get-balance tool
const result = await callTool("get-balance", {
  chainId: "1",
  address: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
});

Solución de problemas

Si encuentra problemas con las dependencias:

# MCP SDK issue - install directly from GitHub
npm uninstall @modelcontextprotocol/sdk
npm install modelcontextprotocol/typescript-sdk

Para problemas de conexión a la base de datos, consulte la Guía de configuración de la base de datos .

Licencia

Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.

Available Tools

5 tools
get-balanceGet native balanceA
Read-only

Get an address's native-token balance (e.g. ETH) on a given chain.

ParametersJSON Schema
NameRequiredDescriptionDefault
addressYesThe wallet/contract address to check.
chainIdYesChain id, e.g. "1" for Ethereum or "11155111" for Sepolia.

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true and openWorldHint=true, so the agent knows it's a safe, read-only operation. The description clarifies the asset type (native token) but adds no further behavioral traits like error handling or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence containing all essential information with no redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple balance query tool with readOnlyHint, the description is largely complete. However, it omits the return format (e.g., wei or decimal) and potential error conditions, which could be helpful given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with descriptions for both parameters (address, chainId). The description adds context about native tokens but no additional parameter-level details beyond what the schema provides, aligning with baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and identifies the resource ('native-token balance') with an example ('ETH'). It clearly states the scope ('on a given chain'), differentiating it from sibling tools like 'get-chains' or 'get-transaction-status'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts where it is appropriate, or when to avoid it, such as for token balances other than native.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-chainsList supported chainsA
Read-only

List the blockchain networks this server supports, with their chain ids and native currencies.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (dynamic results). The description adds that it returns chain ids and native currencies, which is consistent and adds value. No further behavioral traits disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with the verb and resource, no extraneous words. Each word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters, no output schema, and annotations covering safety and dynamism, the description is fully adequate for a simple listing tool. It specifies what is returned (chain ids and native currencies) without needing more.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist (schema coverage 100%), so the description's job of explaining the tool's action is fulfilled. The description adds meaning beyond the empty schema by detailing the output content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists blockchain networks with chain ids and native currencies. The verb 'list' and resource 'supported chains' are specific and distinguish it from siblings like get-balance or prepare-transaction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives given, but the context implies it is for retrieving supported networks. Since siblings are functionally distinct, no exclusion guidance is needed, though mentioning its use as a prerequisite could improve clarity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-transaction-statusGet transaction statusA
Read-only

Check the current status of a prepared transaction by its id.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe transaction id returned by prepare-transaction.

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds 'current status', implying time-sensitivity, beyond the readOnlyHint and openWorldHint annotations. However, it does not disclose what the status entails, potential behaviors, or any side effects, leaving some ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. Every word serves a purpose, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, annotations present), the description is minimally adequate but lacks clarity on the return value or possible status types, which could improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear parameter description. The tool description adds no additional meaning beyond what is already in the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'check', the resource 'status of a prepared transaction', and the method 'by its id'. It distinguishes from siblings like get-balance and prepare-transaction by focusing on transaction status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a transaction id from prepare-transaction, but it does not explicitly state when to use or when not to use this tool, nor does it mention alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

prepare-transactionPrepare a transaction for signingA

Create an unsigned transaction and return a URL the user opens to review and sign it in their own wallet. Private keys never reach this server. Share the returned URL with the user.

ParametersJSON Schema
NameRequiredDescriptionDefault
toYesRecipient address.
dataNoCalldata hex for contract interactions. Defaults to "0x".
valueNoAmount of native token to send, e.g. "0.01". Defaults to "0".
chainIdYesChain id, e.g. "1".
gasLimitNoOptional gas limit (integer). The wallet estimates if omitted.

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds value beyond annotations by disclosing that private keys never reach the server, a key security trait. With annotations already indicating openWorldHint=true, the description reinforces the user-involved workflow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste. Purpose is front-loaded and essential information is efficiently conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the description explains the return is a URL for the user to review and sign. This covers the essential output without needing further detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and parameter descriptions in the schema are clear. The description does not need to duplicate param details, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates an unsigned transaction and returns a URL for user signing. It distinguishes itself from sibling tools which are read-only or informational (get-balance, get-chains, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing to prepare a transaction for signing, but does not explicitly state when not to use or provide alternatives. It gives practical instructions (share URL with user) but lacks exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

read-contractRead a smart contractA
Read-only

Call a read-only (view/pure) contract method. Provide abi as human-readable signatures (e.g. ["function balanceOf(address) view returns (uint256)"]) for zero-config use, or set ETHERSCAN_API_KEY to auto-fetch verified ABIs.

ParametersJSON Schema
NameRequiredDescriptionDefault
abiNoOptional ABI: a signature string, array of signatures, or JSON ABI.
argsNoArguments for the method, in order.
methodYesMethod name to call, e.g. "balanceOf".
addressYesContract address.
chainIdYesChain id, e.g. "1".

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint and openWorldHint. Description adds behavioral context: calls view/pure methods, details ABI handling (zero-config or auto-fetch). No contradictions. Adequate beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences; first sentence states core purpose, second explains ABI configuration. No unnecessary words, front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and generic nature of the tool, the description sufficiently covers how to invoke it. Mentions zero-config and Etherscan integration. Could optionally mention return format, but not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds specific meaning for the abi parameter (how to provide signatures or use Etherscan), going beyond the schema's generic 'Optional ABI' description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calls read-only (view/pure) contract methods, with specific verb and resource ('call a... contract method'), and distinguishes from sibling tools like prepare-transaction by emphasizing read-only.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for when to use (calling read-only methods) and explains ABI provision options (human-readable signatures or Etherscan). Implicitly excludes state-changing methods, but no explicit when-not-to-use statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updatesv0.4.0
    • First observedget-balance
    • First observedget-chains
    • First observedget-transaction-status
    • First observedprepare-transaction
    • First observedread-contract
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct blockchain operation: balance query, chain listing, transaction status, transaction preparation, and contract reading. No functional overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., get-balance, prepare-transaction). No mixing of styles.

Tool Count5/5

With 5 tools, the server covers core blockchain interactions without being excessive or too sparse. Each tool serves a clear purpose.

Completeness4/5

The tool set covers essential operations: balance, chain info, contract reading, and transaction lifecycle. Missing features like event log retrieval or gas estimation, but for basic blockchain interactions it is largely complete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches