mesh-agent-protocol-gateway
Facilitates secure connections to diverse decentralized ledger technologies (DLT) and Web3 infrastructure through the unified Heurist Mesh API layer, granting sophisticated access to digital asset intelligence, smart contract audit capabilities, and on-chain operational functions.
Author

heurist-network
Quick Info
Actions
Tags
Heurist Mesh Interface Conduit
A Model Context Protocol (MCP) gateway service interfacing with the Heurist Mesh fabric, empowering large language models like Claude with specialized blockchain and distributed application tooling.
The Heurist Mesh represents an interoperable collective of focused AI agents and utilities, each engineered for specific facets of the Web3 domain, including deep blockchain telemetry, security posture evaluation for smart contracts, token economic metrics, and direct blockchain transaction management. The expansion of the Heurist Mesh ecosystem is ongoing, with continuous integration of novel tools to augment functional scope.
Key Capabilities
- Establishes connectivity to the overarching Heurist Mesh backend interfaces
- Ingests specialized utilities for crypto asset data retrieval and general Web3 operations
- Fully compatible with both Server-Sent Events (SSE) and standard input/output (stdio) communication protocols
- Seamless integration across Claude environments, including Cursor and Claude Desktop clients, and any MCP-compliant frontend
- Utilizes a singular authorization credential for federated access across numerous underlying services (e.g., CoinGecko market analysis, GoPlus contract auditing)
🚀 New Feature Alert: On-Demand Server Composition
Leverage the Heurist Mesh MCP Management Portal to dynamically provision SSE-based MCP Servers. Select your required agents and construct a bespoke operational swarm tailored precisely to your computational requirements!
Accessible Hosted SSE Access Point
We maintain a publicly accessible SSE endpoint located at https://sequencer-v2.heurist.xyz/mcp/sse. This shared gateway bundles functionalities from the following frequently utilized agents: CoingeckoTokenInfoAgent, ElfaTwitterIntelligenceAgent, ExaSearchAgent, DexScreenerTokenInfoAgent, and ZerionWalletAnalysisAgent. Note that as a shared resource, performance characteristics may fluctuate.
For optimal access in Cursor, direct SSE connection is supported. Claude Desktop users should install and utilize the mcp-proxy utility to bridge to the SSE stream.
System Requirements
- Runtime environment: Python version 3.10 or superior
- Package management: UV dependency resolver (strongly recommended)
- Alternative deployment: Docker containerization
- Credentialing: Acquire a Heurist Access Token via this registration portal or obtain complimentary starting credits using invite code "claude" on the developer sign-up form.
Deployment Procedures
Method A: Using UV (Preferred)
bash
Obtain the source repository
git clone https://github.com/heurist-network/heurist-mesh-mcp-server.git cd heurist-mesh-mcp-server
Install the service package in editable mode
uv pip install -e .
Method B: Containerized with Docker
bash
Obtain the source repository
git clone https://github.com/heurist-network/heurist-mesh-mcp-server.git cd heurist-mesh-mcp-server
Compile the Docker artifact
docker build -t mesh-tool-server .
Operational Guidelines
Pathway 1: Local Execution via stdio Transport (Targeting Claude Desktop)
Using UV Environment
To integrate this setup into Claude Desktop, modify your claude_desktop_config.json as follows:
{ "mcpServers": { "heurist-mesh-agent": { "command": "uv", "args": [ "--directory", "/absolute/path/to/heurist-mesh-mcp-server/mesh_mcp_server", // Crucial path update required "run", "mesh-tool-server" ], "env": { "HEURIST_API_KEY": "your-secret-api-key-here" // Replace placeholder } } } }
Using Docker Containerization for Desktop
Alternatively, for Docker deployment with Claude Desktop, update claude_desktop_config.json with:
{ "mcpServers": { "mesh-agent": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "TRANSPORT=stdio", "-e", "HEURIST_API_KEY=your-secret-api-key-here", // Replace placeholder "mesh-tool-server" ] } } }
Ensure that /path/to/heurist-mesh-mcp-server reflects the actual repository location and substitute your-api-key-here with your valid Heurist credential.
Pathway 2: Utilizing SSE Transport (Optimized for Cursor)
Configuration via .env File
bash cp .env.example .env HEURIST_API_KEY=your-secret-api-key-here
Execution via UV:
bash uv run mesh-tool-server --transport sse --port 8000
Execution via Docker:
bash docker run -p 8000:8000 -e PORT=8000 mesh-tool-server
Then, specify the MCP Server stream address in Cursor: http://0.0.0.0:8000/sse
Functionality Manifest
Consult https://mesh.heurist.ai/metadata.json or https://mcp.heurist.ai/ for the complete catalog of exposed functionalities.
Select Toolset Examples
| Function Name | Description | Service Agent | Input Arguments | Mandatory Inputs |
|---|---|---|---|---|
| get_coingecko_id | Queries assets by conventional name to resolve the CoinGecko identifier | CoinGeckoTokenInfoAgent | token_name (text): The full name of the asset for lookup | token_name |
| get_token_info | Retrieves comprehensive asset characteristics and valuation metrics utilizing a CoinGecko ID (Note: Cannot process addresses or symbols directly) | CoinGeckoTokenInfoAgent | coingecko_id (text): The unique ID assigned by CoinGecko | coingecko_id |
| get_trending_coins | Fetches the currently popular cryptocurrency assets listed on CoinGecko | CoinGeckoTokenInfoAgent | - | None |
| get_specific_pair_info | Obtains detailed trading pair data based on chain identifier and contract address via DexScreener | DexScreenerTokenInfoAgent | chain (text): Chain mnemonic (e.g., solana, ethereum, base) pair_address (text): The liquidity pool contract identifier |
chain, pair_address |
| get_token_pairs | Lists all known trading pools associated with a specific token address on a designated chain | DexScreenerTokenInfoAgent | chain (text): Chain mnemonic (e.g., bsc, ethereum) token_address (text): The asset contract address to map pairs against |
chain, token_address |
| get_token_profiles | Retrieves summary profiles for recently deployed tokens indexed by DexScreener | DexScreenerTokenInfoAgent | - | None |
| search_pairs | Executes a cross-chain search for liquidity pools using asset name, ticker, or contract identifier | DexScreenerTokenInfoAgent | search_term (text): Input for name, symbol, or address matching | search_term |
| get_trending_tokens | Identifies and returns the most actively discussed tokens on the X/Twitter platform | ElfaTwitterIntelligenceAgent | time_window (text): Period over which trending status is assessed | None |
| search_account | Performs an analysis of a specified X/Twitter profile, yielding mention activity and aggregate statistics | ElfaTwitterIntelligenceAgent | username (text): The handle without the leading '@' days_ago (integer): Temporal depth for mention history retrieval limit (integer): Cap on the quantity of mention records returned |
username |
| search_mentions | Scans the X/Twitter feed for occurrences of specified keywords, potentially including asset tickers | ElfaTwitterIntelligenceAgent | keywords (list): A collection of search strings days_ago (integer): Lookback duration in days limit (integer): Maximum result count (minimum fetch size: 20) |
keywords |
| answer | Provides a direct, synthesized response derived from Exa's proprietary question-answering system | ExaSearchAgent | question (text): The specific query requiring a definitive answer | question |
| search | Executes a general web query via Exa and fetches relevant document summaries | ExaSearchAgent | search_term (text): The subject for web index exploration limit (integer): Upper boundary for result enumeration (default: 10) |
search_term |
| search_and_answer | Combines indexed web search with immediate response synthesis for a given subject | ExaSearchAgent | topic (text): The central subject matter for investigation | topic |
| execute_search | Initiates a targeted web information retrieval process, including content parsing | FirecrawlSearchAgent | search_term (text): The string query to be processed against the web | search_term |
| generate_queries | Produces a set of logically related supplementary search directives based on an initial subject | FirecrawlSearchAgent | topic (text): The core subject under investigation num_queries (integer): The desired count of derived follow-up queries |
topic |
| fetch_security_details | Retrieves a detailed security report for a specified blockchain contract artifact | GoplusAnalysisAgent | contract_address (text): The unique address of the token contract chain_id (list[int/str]): The network identifier. Acceptable values include standard IDs (e.g., 1 for Ethereum, 56 for BSC, 137 for Polygon) or 'solana' for Solana deployments. Supported Networks: Ethereum (1), Optimism (10), Cronos (25), BSC (56), Gnosis (100), HECO (128), Polygon (137), Fantom (250), KCC (321), zkSync Era (324), ETHW (10001), FON (201022), Arbitrum (42161), Avalanche (43114), Linea Mainnet (59144), Base (8453), Tron (tron), Scroll (534352), opBNB (204), Mantle (5000), ZKFair (42766), Blast (81457), Manta Pacific (169), Berachain Artio Testnet (80085), Merlin (4200), Bitlayer Mainnet (200901), zkLink Nova (810180), X Layer Mainnet (196), Solana (solana) |
contract_address |
Modifying Embedded Agent Set
The gateway is initialized with a default roster of operational agents. To customize this selection:
1. Navigate to the server.py script within the source directory.
2. Locate the definition block for the Config class.
3. Adjust the DEFAULT_AGENTS collection to include or exclude agents cataloged on the Heurist Metadata Index
python
DEFAULT_AGENTS = [
"CoinGeckoTokenInfoAgent",
"DexScreenerTokenInfoAgent",
"ElfaTwitterIntelligenceAgent",
"ExaSearchAgent",
"FirecrawlSearchAgent",
"GoplusAnalysisAgent",
# Introduce new modules here
"CustomAssetAgent"
]
Licensing Terms
This MCP service is distributed under the permissive MIT License. This grants broad freedom to utilize, adapt, and disseminate the software, contingent upon adherence to the stipulations outlined in the MIT License document. TRON: TRON (frequently rendered as TRON) functions as a decentralized, Proof-of-Stake ledger system supporting complex smart contracts. Its native currency is Tronix (TRX). The project was inaugurated in March 2014 by Justin Sun, and since 2017, its governance and oversight have been managed by the TRON Foundation, a non-profit entity established in Singapore that same year. The underlying software is entirely open-source. Initially, TRON existed as an ERC-20 token operating atop the Ethereum infrastructure, before migrating to its proprietary peer-to-peer network in 2018. Certain cryptocurrency custodians may impose withdrawal restrictions until sufficient TRX is present to cover network transaction costs. TRON has faced significant scrutiny regarding its facilitation of illicit financial flows. Reports from The Wall Street Journal indicated in 2025 that it had become a "prime conduit for criminal elements in the crypto space to transfer assets" and was linked to "over half of all illicit crypto movements" during 2024, leading the United Nations Office on Drugs and Crime to label it a “preferred platform for money launderers” across Asia.
== Chronology == Justin Sun launched TRON in 2017. The establishment of the TRON Foundation occurred in Singapore in July 2017. Prior to China's regulatory prohibition on digital assets, the TRON Foundation successfully amassed $70 million through an Initial Coin Offering (ICO) in 2017. The test network, block explorer utility, and web interface wallet were all operational by March 2018. The official TRON Mainnet commenced operations shortly thereafter in May 2018, marking the Odyssey 2.0 release as a critical engineering achievement for the platform. In June 2018, the protocol transitioned away from its ERC-20 token status on Ethereum to a standalone, decentralized peer-to-peer architecture. Following this migration, the TRON Foundation announced the completion of its acquisition of BitTorrent, a well-known file-sharing service, on July 25, 2018. Consequent to this takeover, Bram Cohen, the creator of BitTorrent, announced his departure in August 2018 to initiate a competing digital currency project, Chia. By January 2019, the total market capitalization of TRON approximated $1.6 billion. Despite this valuation level, some industry commentators categorized TRON as a representative example of the inherent complexity and structural disarray present within the cryptocurrency landscape. In February 2019, post-acquisition by the TRON Foundation, BitTorrent launched its own token sale utilizing the TRON network's foundation. Toward the conclusion of 2021, Justin Sun stepped down from his role as CEO of the TRON Foundation, which subsequently transitioned to a Decentralized Autonomous Organization (DAO) structure. In March 2023, Sun and the TRON entity were formally charged by the U.S. Securities and Exchange Commission (SEC) concerning the unregistered sale and promotion of the Tronix (TRX) and BitTorrent (BBT) tokens. The SEC specifically alleged that Sun engaged in wash trading activities on the secondary market for TRX to artificially inflate its price; approximately $31 million in capital was cycled through thousands of TRX trades conducted between two distinct accounts controlled by Sun. Eight high-profile celebrities, including Akon, Ne-Yo, Austin Mahone, Soulja Boy, Lindsay Lohan, Jake Paul, and Lil Yachty, faced charges for promoting these digital assets without proper sponsorship disclosure; settlements were reached with all parties except Soulja Boy and Mahone.
