AgentHubAgentHub

Pulse Verity MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.pipeworx-io/pulse-verity · v0.1.1

Pulse Verity — crypto index prices that come with a PROOF.

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Pulse Verity — crypto index prices that come with a PROOF. Pulse Verity is a MCP Server listed from MCP Registry. Transports: streamable-http. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHubCursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; if you already have MCPs, merge only this entry under mcpServers
  3. Save, then Cmd+Shift+P (Ctrl+Shift+P on Windows) → Reload Window
Click to copy snippet
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Setup tutorial

  1. Open the Pulse Verity page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (remote)

  1. Install Claude Code CLI (claude must work in your terminal)
  2. Click Copy config below, paste into terminal, and run
  3. Restart Claude Code after it succeeds
claude mcp add --transport http pulse-verity https://gateway.pipeworx.io/pulse-verity/mcp

Cursor — .cursor/mcp.json (remote)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; if you already have MCPs, merge only this entry under mcpServers
  3. Save, then Cmd+Shift+P (Ctrl+Shift+P on Windows) → Reload Window
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

VS Code — .vscode/mcp.json (remote)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Save and Developer: Reload Window
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Claude Desktop — claude_desktop_config.json (remote)

  1. Open Claude Desktop config: macOS ~/Library/Application Support/Claude/claude_desktop_config.json; Windows %APPDATA%\Claude\claude_desktop_config.json
  2. Click Copy config and merge under mcpServers
  3. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Trae — .trae/mcp.json (remote)

  1. Trae → Settings → MCP, or edit .trae/mcp.json (project) / global mcp.json
  2. Use Manual add / Raw JSON, click Copy config and paste; merge only this mcpServers entry
  3. Save, pick an MCP-capable agent (e.g. Builder with MCP), reload window if needed
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Cherry Studio — MCP settings (remote)

  1. Cherry Studio → Settings → MCP Servers
  2. Add via JSON import or SSE/HTTP with the URL
  3. Click Copy config, paste the mcpServers entry, then enable the server
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Tongyi Lingma — MCP config (remote)

  1. Tongyi Lingma: avatar → Settings → MCP (agent mode; plugin ~v2.5+)
  2. Click + → config file or manual SSE/HTTP with the service URL
  3. Click Copy config and merge JSON; a healthy icon means connected
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Cline — MCP Servers (remote)

  1. VS Code Cline panel → settings gear → MCP Servers
  2. Click Copy config and paste the mcpServers entry into Cline
  3. Save; Cline reconnects and shows tools
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (remote)

  1. WorkBuddy: sidebar Plugins → MCP Servers → Configure MCP; or edit ~/.workbuddy/mcp.json (user) / .workbuddy/mcp.json (project)
  2. Click Copy config and merge under mcpServers (Tencent WorkBuddy / CodeBuddy)
  3. Save; status should turn green — fully restart the client if needed
{
  "mcpServers": {
    "pulse-verity": {
      "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Windsurf — mcp_config.json (remote)

  1. Edit ~/.codeium/windsurf/mcp_config.json (Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json)
  2. Click Copy config and merge; remote MCP must use serverUrl (not url)
  3. Save and refresh MCP in Windsurf Cascade
{
  "mcpServers": {
    "pulse-verity": {
      "serverUrl": "https://gateway.pipeworx.io/pulse-verity/mcp"
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for Pulse Verity

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for Pulse Verity?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Tool calls timing out or failing to download packages?

First-time package downloading might be slow or timeout due to network limits. Configure a reliable mirror or check outbound proxy settings.

Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

Pulse Verity Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: pulse_verityExecute the core tool interface of Pulse Verity
Request ArgumentsJSON Schema
{
  "target": "Pulse Verity",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

Pulse Verity + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: Pulse Verity
HTML
<a href="https://myagenthub.cn/p/io.github.pipeworx-io/pulse-verity" title="Listed on AgentHub: Pulse Verity" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.pipeworx-io/pulse-verity?lang=en" alt="Listed on AgentHub: Pulse Verity" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: Pulse Verity](https://myagenthub.cn/badge/io.github.pipeworx-io/pulse-verity?lang=en)](https://myagenthub.cn/p/io.github.pipeworx-io/pulse-verity)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.pipeworx-io/pulse-verity",
  "type": "mcp-server",
  "version": "0.1.1",
  "displayName": "Pulse Verity",
  "description": "Pulse Verity — crypto index prices that come with a PROOF.",
  "repository": {
    "url": "https://github.com/pipeworx-io/mcp-pulse-verity",
    "source": "github"
  },
  "homepage": "https://pipeworx.io/packs/pulse-verity",
  "distribution": {
    "packages": [],
    "remotes": [
      {
        "transport": "streamable-http",
        "url": "https://gateway.pipeworx.io/pulse-verity/mcp"
      }
    ]
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.pipeworx-io/pulse-verity",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.pipeworx-io%2Fpulse-verity/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}
Pulse Verity MCP Setup & Guide - AgentHub