MCP Hub
Back to servers

DeBanK

MCP (Model Context Protocol) Server. Provides a bridge to blockchain and DeFi data across multiple chains, enabling access to information about protocols, tokens, pools, user assets, activities, and wallet operations

Stars
8
Tools
9
Validated
Jan 11, 2026

DeBanK MCP Server

A stateless Model Context Protocol (MCP) server for interacting with the DeBanK API to retrieve blockchain and DeFi data.

Overview

This project implements a Model Context Protocol (MCP) server that provides various tools for querying blockchain data, including chains, protocols, tokens, pools, and user assets. Built with the @modelcontextprotocol/sdk, it leverages the HTTP Streamable transport to provide a modern, efficient API interface.

The server is designed to be completely stateless, with each request being handled independently, making it highly scalable and robust for production environments.

Features

  • Stateless Architecture: Each request creates a new server instance and transport
  • Comprehensive DeFi Data Tools: Access to chains, protocols, tokens, pools, and user data
  • Pagination Support: All list-returning endpoints support pagination
  • Error Handling: Robust error handling and reporting

Tools Available

Tool NameDescription
get_chain_infoGet information about blockchains
get_protocol_infoGet information about DeFi protocols
get_token_infoGet information about tokens
get_pool_infoGet detailed information about a specific liquidity pool
get_user_assetsGet information about a user's assets across different blockchains
get_user_activitiesGet information about a user's protocol positions, transaction history, and balance charts
get_user_authorizationsGet information about a user's token and NFT authorizations
get_collection_nft_listGet a list of NFTs in a specific collection
wallet_toolsAccess wallet-related functionality

Prerequisites

Installation

  1. Clone the repository
git clone https://github.com/yourusername/debank-mcp-server.git
cd debank-mcp-server
  1. Set up your environment variables
export ACCESS_KEY=your_debank_api_key

Running the Server

Start the server with the following command:

deno run --allow-net --allow-env main.ts

The server will start and listen on port 8080 by default. You can now send MCP requests to http://localhost:8080/mcp.

MCP HTTP Streamable Implementation

This project uses the StreamableHTTPServerTransport from the Model Context Protocol SDK to handle MCP requests. Every request creates a new server instance and transport, making the service completely stateless:

// Create new server instance and transport for each request
const server = createServer();
const transport = new StreamableHTTPServerTransport({
  sessionIdGenerator: () => randomUUID(),
});

// Connect to server
await server.connect(transport);

// Handle request
await transport.handleRequest(req, res, req.body);

This approach simplifies deployment and scaling, as there's no need to manage session state across multiple instances.

Project Structure

├── main.ts                # Main server file with MCP endpoint handling
├── deno.json              # Deno configuration
├── deno.lock              # Dependency lock file
├── tool/
│   ├── toolInfo.ts        # Tool definitions
│   └── toolHandler.ts     # Tool handler implementations
└── README.md              # This file

Configuration

The following environment variables can be configured:

  • ACCESS_KEY - Your DeBanK API access key
  • PORT - (Optional) Port to run the server on (default: 8080)

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

Reviews

No reviews yet

Sign in to write a review