MCP Server

What @openpulsechain/mcp-server MCP server does

The @openpulsechain/mcp-server MCP server gives AI assistants access to analytics for the PulseChain ecosystem. Its coverage includes token safety scores from 0 to 100, honeypot detection, deployer and contract analysis, wallet profiles, whale activity, smart-money tracking, scam alerts, DEX volume, bridge flows, and holder league rankings.

The repository describes 20 MCP tools. The listing divides these into 11 free tools and 9 pro tools, while the README presents the MCP component as part of a broader OpenPulsechain platform. Other platform modules include a web dashboard, REST and safety APIs, indexers, a Chrome extension, and Dune bridge analytics; those modules are separate from the MCP server’s role.

How it works

OpenPulsechain collects data through Python indexers and stores it in PostgreSQL. Sources include the PulseX Subgraph, PulseChain RPC, DefiLlama, Blockscout, bridge subgraphs and APIs, Dune Analytics, and on-chain honeypot simulations using a FeeChecker contract. The MCP layer makes selected analytics available to AI assistants rather than requiring an agent to query each source independently.

Available data includes more than 2,500 discovered tokens, historical price records dating from May 2023, and bridge transfers from OmniBridge and Hyperlane, according to the project material. Token prices on PulseChain are sourced from PulseX derivedUSD values. Safety analysis considers factors such as honeypot behavior, contract characteristics, liquidity-provider health, holder concentration, and token age.

Setup and configuration

The repository’s setup instructions place the MCP project in the mcp-server/ directory. The documented build flow is:

npm install
npm run build

The project listing also provides this package-based launch command:

npx @openpulsechain/mcp-server

No environment variables or API credentials are specified in the supplied material for running the MCP server. The README identifies the underlying data sources as public or on-chain, although Dune access has a stated public allowance of 2,500 credits per month for its bridge queries.

Tools and capabilities

The @openpulsechain/mcp-server MCP server is suited to agent workflows that need to:

• Inspect a token’s safety score and risk indicators.
• Check tokens for suspected honeypot behavior.
• Review whale holdings, wallet activity, and funding relationships.
• Find large PulseX swaps and follow smart-money activity.
• Detect scam-related events such as liquidity removals and whale dumps.
• Examine PulseX trading volume, bridge flows, and holder league rankings.

The broader platform refreshes some analytics on schedules rather than continuously: scam scanning runs every 30 minutes, smart-money data refreshes every 60 seconds, and holder leagues update every six hours. These refresh intervals describe the platform data and may affect how current an MCP response is.

Limitations and notes

Results are limited to PulseChain-focused coverage and the sources indexed by OpenPulsechain. The project states that its data is informational only and is not financial advice. It also states that OpenPulsechain is not affiliated with PulseChain, PulseX, or related entities. Dune-based bridge analytics are subject to the service’s public credit allowance. The supplied documentation does not identify specific MCP client applications or provide a detailed per-tool schema.