Log inSubmit server
MCP Server logo

MCP Server

by @openpulsechain

Query PulseChain prices, token safety, liquidity, wallets, whales, scams, and bridge activity through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "openpulsechain-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@openpulsechain/mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 28 tools correctly (12d ago).

Overview

@openpulsechain/mcp-server gives MCP-compatible assistants read-only access to real-time PulseChain analytics. It includes 11 tools for prices, token metadata, market activity, liquidity, safety checks, honeypots, bridges, and holder distribution, plus 9 API-key-gated tools for AML, wallet, tracing, and smart-money analysis. The server runs through npx and uses an optional OPENPULSECHAIN_API_KEY to enable Pro mode. Reach for it when an agent needs PulseChain market or contract intelligence without wallet signing or write operations.

Use cases

  • Check a token for honeypot behavior, taxes, and ownership risk
  • Compare PulseChain tokens and PulseX pairs by volume or liquidity
  • Monitor bridge inflows, outflows, and network market activity
  • Investigate whale movements and wallet funding sources
  • Review wallet exposure, swaps, and address-risk indicators

Key features

  • 11 no-auth PulseChain analytics tools
  • 9 API-key-gated Pro tools
  • Token safety and honeypot analysis
  • Wallet, whale, and funding-trace analysis
  • Core-token address resource
  • Read-only operation with no wallet signing

Tools28

What MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~2.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

96/96 checks healthy over the last 75d

What it can do

From the 28 tools this server returned when we ran it; 28 declare their own safety hints.

Handles credentials · 17Makes network requests · 28Read-only tools · 28
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age177 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @openpulsechain/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads190Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed28Callable tools this server registers over MCP.
Directory activity10 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server works

What @openpulsechain/mcp-server does

@openpulsechain/mcp-server exposes PulseChain on-chain analytics to MCP clients. Its free tier covers current token prices, token metadata, historical OHLCV data, ranked tokens and pairs, network-level market statistics, token safety analysis, liquidity, detected honeypots, bridge flows, and holder distribution tiers.

A Pro tier adds address-risk checks, deployer reputation, scam alerts, large-wallet activity, large PulseX swaps, wallet balances, wallet swap history, funding-source tracing, and holder rankings. The server also publishes a pulsechain://tokens/core resource containing addresses for WPLS, HEX, PLS, PLSX, INC, eHEX, DAI, USDC, USDT, WETH, and WBTC.

How it works

The server runs as a local stdio process launched with npx. It retrieves analytics from api.openpulsechain.com and safety, alert, tracing, and league data from safety.openpulsechain.com. Those backends source information from the PulseX Subgraph, Blockscout Explorer, and on-chain RPC calls.

Without an API key, the 11 standard tools are available. Supplying OPENPULSECHAIN_API_KEY switches the process to Pro mode and makes all 20 tools callable. Pro requests send the key as a bearer token to the backend; the key is not cached by the server.

Setup and configuration

Run the server directly with:

Terminal
npx @openpulsechain/mcp-server

For Claude Desktop, add an MCP entry that runs npx -y @openpulsechain/mcp-server as the command and argument. Claude Code uses the same command in .claude/settings.json. Cursor is also named as a supported MCP client.

To activate Pro tools, add the API key to the MCP server environment:

config.json
{
  "env": {
    "OPENPULSECHAIN_API_KEY": "sk-opk-..."
  }
}

Keys are available through the OpenPulseChain pricing page.

Tools and capabilities

The 11 standard tools provide:

  • Current prices, 24-hour changes, volume, and market capitalization
  • Token details such as decimals, liquidity, and holders
  • Up to 30 days of historical price data without an API key
  • Rankings for tokens and PulseX trading pairs
  • Network TVL, volume, gainers, and losers
  • Honeypot detection, buy and sell taxes, and ownership grades
  • Liquidity breakdowns, recent honeypots, bridge flows, and holder leagues

The nine Pro tools support sanctions and exploit checks, deployer history, scam alerts, whale activity, large swaps, wallet balances, wallet swap history, two-level funding traces, and holder ranking.

Limitations and notes

The server is read-only: it does not sign transactions, access seed phrases, or perform write operations. Requests are rate-limited by the backend, with stricter limits without an API key. Historical token data is limited to 30 days in the standard tier. Calling a Pro tool without a key returns a pro_tier_required error.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server

@openpulsechain is an MCP server that connects AI assistants to PulseChain on-chain analytics. Its main tools cover token prices, metadata, liquidity, market activity, safety and honeypot checks, bridge statistics, holder leagues, wallets, whale activity, scam alerts, and funding traces, with advanced tools requiring an API key.

Run `npx @openpulsechain/mcp-server` or configure an MCP client to launch `npx -y @openpulsechain/mcp-server`. Claude Desktop uses its MCP configuration file, while Claude Code uses `.claude/settings.json`.

Set the `OPENPULSECHAIN_API_KEY` environment variable in the server configuration. The server then starts in Pro mode and exposes all 20 tools; without the key, Pro tool calls return a `pro_tier_required` error.

Yes, Cursor is named as a supported client for @openpulsechain/mcp-server. Configure Cursor to launch the server with `npx -y @openpulsechain/mcp-server`; the standard tools work without an API key.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/-openpulsechain-mcp-server?style=directory)](https://allmcps.com/mcp/-openpulsechain-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/-openpulsechain-mcp-server"><img src="https://allmcps.com/api/badge/-openpulsechain-mcp-server?style=directory" alt="MCP Server on AllMCPs" /></a>