pickfit

BrowseMCP servers

pulsechain-mcp

MCP server letting AI agents read PulseChain data and use encrypted wallets.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 4 known high or critical vulnerabilities (5 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:@modelcontextprotocol/node 2.0.0 MCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length (GHSA-f897-62hf-6gxq, high, fixed in 2.1.0)
  • npm:@modelcontextprotocol/server 2.0.0 MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation (GHSA-46jr-4wx8-v453, high, fixed in 2.3.0)
See 3 more

Linux x86_64

You need first

  • Runtimes: Node.js 24.22.1
  1. git clone https://github.com/DavidFeder/pulsechain-mcp.git

    git clone https://github.com/DavidFeder/pulsechain-mcp.git
  2. npm install (triggers build via prepare)

    cd pulsechain-mcp && npm install

Add it to your agent

claude mcp add pulsechain-mcp -- node '<install-folder>/dist/index.js'
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "pulsechain-mcp": {
      "command": "node",
      "args": [
        "<install-folder>/dist/index.js"
      ]
    }
  }
}

Replace <install-folder> with the folder you ran the install steps in.

Add the server to your MCP client from the cloned pulsechain-mcp folder, then ask your agent to call pulsechain_health to confirm it is connected.

What it does

  • Look up PulseChain data and research markets
    Not shown working
  • Review and create smart contracts
    Not shown working
  • Get swap quotes and prices and run swaps
    Not shown working
  • Send PLS and tokens from agent wallets
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Needs the network

Good for

  • Check which pHEX stakes end in the next 30 days
  • Check PulseX buy and burn status and PLSX in dead address
  • Check if a Pump.tires coin is on the curve or graduated
  • Get swap quotes and execute swaps

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Needed the network
  • Checked on 1 Nov 2026
  • Version 1.0.13

An MCP client handshake over stdio listed 80 tools, and a call to pulsechain_health returned a result.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.