Log inSubmit server
Pulsenetwork MCP logo

Pulsenetwork MCP

by GTCC777

Accesses dozens of domain-specific intelligence APIs through MCP, with per-query USDC payments on Base.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pulsenetwork MCP

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": {
    "gtcc777-pulsenetwork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-pulsenetwork"
      ],
      "env": {
        "AGENT_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

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

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 80 tools correctly (1mo ago).

Overview

GTCC777/pulsenetwork-mcp MCP server connects MCP clients to PulseNetwork’s domain-specific intelligence APIs through one interface. Requests are paid per query with USDC through x402 on Base mainnet, and the server uses a wallet private key rather than an API key. Reach for GTCC777/pulsenetwork-mcp MCP server when an agent needs on-demand, cross-domain research or a discovery tool to select an appropriate vertical.

Use cases

  • Discover a suitable intelligence vertical for an agent request
  • Query market and sports research endpoints on demand
  • Build a multi-domain research or monitoring agent
  • Retrieve per-query climate, career, healthcare, or compliance intelligence

Key features

  • Single MCP interface for many intelligence verticals
  • Discover meta-tool for locating relevant APIs
  • x402 USDC payments on Base mainnet
  • Per-query pricing without an API key
  • Multi-domain research and analysis endpoints
  • Language selection through the lang parameter

Tools80

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

Verified live~72.7k 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 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · mcp-pulsenetwork (npm)

Adoption & maintenance

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

GitHub stars3Stargazers on the source repository.
npm downloads367Package downloads in the last 30 days.
Last commit7d 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 exposed80Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Pulsenetwork MCP works

What GTCC777/pulsenetwork-mcp MCP server does

GTCC777/pulsenetwork-mcp MCP server gives an MCP client access to PulseNetwork’s collection of specialized intelligence APIs. The documented coverage includes financial and crypto research, market and arbitrage analysis, healthcare costs, clinical trials, regulatory compliance, careers, education, climate, biodiversity, vehicles, construction, collectibles, sports, and fandom research.

The repository README describes 73 intelligence verticals and 851 endpoints. Each vertical groups related operations behind named endpoints, such as forecast, salary, cve-brief, filing, species, or match-preview.

How it works

The server exposes a single MCP integration rather than requiring a separate connection for each vertical. Agents can call the discover meta-tool to find relevant PulseNetwork options across the network.

Queries are priced individually. The stated range is $0.015 to $1.00 per request, although the supplied endpoint listings show prices that vary by vertical and operation. Payments use the x402 protocol with USDC on Base mainnet. The payment details identify Base as eip155:8453 and provide the USDC contract address. Some listed material also references Solana for particular payment or network contexts, but the README’s setup instructions specifically require a Base wallet with USDC.

Setup and configuration

Install the package globally with npm install -g mcp-pulsenetwork, or run it directly with npx mcp-pulsenetwork. For a non-interactive MCP client configuration, use npx with the -y flag and pass the package name as an argument.

The required environment variable is AGENT_PRIVATE_KEY. It should contain the private key for a wallet funded with USDC on Base mainnet. The README recommends adding the server to an MCP client configuration with command set to npx, args set to ["-y", "mcp-pulsenetwork"], and the private key supplied through the client’s environment configuration.

Restarting the client after changing its configuration is required for the new server connection to become available.

Tools and capabilities

GTCC777/pulsenetwork-mcp MCP server includes the following documented capabilities:

  • Discover relevant verticals through the discover tool.
  • Query market, crypto, forex, options, futures, prediction-market, and sports intelligence.
  • Research filings, citations, clinical trials, biodiversity, climate, cybersecurity, and regulatory topics.
  • Analyze vehicles, construction projects, careers, education, healthcare prices, debt, deals, collectibles, and consumer products.
  • Request responses using the documented lang parameter and supported language codes.

The exact available tools depend on the installed package and its current PulseNetwork catalog. The listing contains only a subset of the repository’s stated network totals.

Limitations and notes

Using the server requires a funded wallet and incurs a separate USDC charge for paid queries. The service is therefore unsuitable for deployments that cannot securely manage signing credentials or approve per-request blockchain payments.

Prices, coverage, and endpoint availability should be checked through the server’s discovery mechanism and current documentation before an agent relies on a particular vertical. Intelligence outputs cover many specialized domains, but the material does not establish that every endpoint is available in every country or that results replace professional legal, medical, financial, or other expert advice.

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 Pulsenetwork MCP

Run `npx -y mcp-pulsenetwork`, or install it globally with `npm install -g mcp-pulsenetwork`.

Yes. The README provides a Claude Desktop configuration using `npx`, the `mcp-pulsenetwork` package, and the `AGENT_PRIVATE_KEY` environment variable.

It does not require an API key, but it does require an `AGENT_PRIVATE_KEY` for a wallet funded with USDC on Base mainnet.

Individual endpoint prices vary.

Use the `discover` meta-tool to search the available verticals and identify relevant options.

Related MCP servers

All in Aggregators 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 PreviewPulsenetwork MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gtcc777-pulsenetwork-mcp?style=directory)](https://allmcps.com/mcp/gtcc777-pulsenetwork-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/gtcc777-pulsenetwork-mcp"><img src="https://allmcps.com/api/badge/gtcc777-pulsenetwork-mcp?style=directory" alt="Pulsenetwork MCP on AllMCPs" /></a>