Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.MarvelNwachukwu/mcp-pear

NPM · @MARVELCODES/MCP-PEAR · SCANNED OCT 1

MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution.

0 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 66 of 196 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1746 tokens (~87/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.MarvelNwachukwu/mcp-pear server?

io.github.MarvelNwachukwu/mcp-pear runs locally as an npm package, launched with npx -y @marvelcodes/mcp-pear. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @marvelcodes/mcp-pear

# add to Claude Code
claude mcp add marvelnwachukwu-mcp-pear -- npx -y @marvelcodes/mcp-pear
// .cursor/mcp.json
{
  "mcpServers": {
    "marvelnwachukwu-mcp-pear": {
      "command": "npx",
      "args": [
        "-y",
        "@marvelcodes/mcp-pear"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "marvelnwachukwu-mcp-pear": {
      "command": "npx",
      "args": [
        "-y",
        "@marvelcodes/mcp-pear"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add marvelnwachukwu-mcp-pear -- npx -y @marvelcodes/mcp-pear
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marvelnwachukwu-mcp-pear": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@marvelcodes/mcp-pear"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add marvelnwachukwu-mcp-pear --command npx --arg -y --arg @marvelcodes/mcp-pear
# ~/.hermes/config.yaml
mcp_servers:
  marvelnwachukwu-mcp-pear:
    command: "npx"
    args: ["-y", "@marvelcodes/mcp-pear"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "marvelnwachukwu-mcp-pear": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@marvelcodes/mcp-pear"
      ]
    }
  }
}
# add to Vellum
assistant mcp add marvelnwachukwu-mcp-pear -t stdio -c npx -a -y @marvelcodes/mcp-pear
// mcp.json
{
  "mcpServers": {
    "marvelnwachukwu-mcp-pear": {
      "command": "npx",
      "args": [
        "-y",
        "@marvelcodes/mcp-pear"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 1 Oct 2026 · Analysed npm/@marvelcodes/mcp-pear@0.2.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 196 packages
Packages resolved 196
Deprecated 1
Stale 65
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,746 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
adjust_leverage ~69

Change leverage (1-100x) on an existing Pear Protocol position. Higher leverage means greater liquidation risk for the same price move. WRITE: changes risk profile of a live position. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
leverageintegeryes–
positionIdstringyes–

No output schema declared.

No examples provided.

adjust_position ~105

Reduce or increase an existing Pear Protocol position's size by 1-100 percent. executionType: MARKET (immediate) or LIMIT (provide limitRatio). WRITE: changes exposure on a real trade. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
adjustmentSizeintegeryes–
adjustmentTypestringyes–
executionTypestringyes–
limitRationumber––
positionIdstringyes–
referralCodestring––

No output schema declared.

No examples provided.

cancel_order ~68

Cancel a pending Pear Protocol limit, take-profit, or stop-loss order by orderId. Does not affect already-filled portions. For TWAP orders, use cancel_twap_order. WRITE: cancels a live order. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
orderIdstringyes–

No output schema declared.

No examples provided.

cancel_twap_order ~57

Cancel a Pear Protocol TWAP (time-weighted average price) order and all of its remaining unfilled chunks. WRITE: cancels a live order. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
orderIdstringyes–

No output schema declared.

No examples provided.

close_all_positions ~95

Close every open Pear Protocol position with a single executionType (MARKET or TWAP). Returns a per-position result array with success/error. WRITE: executes real trades. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
executionTypestringyes–
randomizeExecutionboolean––
referralCodestring––
twapDurationnumber––
twapIntervalSecondsnumber––

No output schema declared.

No examples provided.

close_position ~108

Close one open Pear Protocol position by positionId. executionType: MARKET (immediate) or TWAP (spread over time; requires twapDuration in seconds). WRITE: executes a real trade. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
executionTypestringyes–
positionIdstringyes–
randomizeExecutionboolean––
referralCodestring––
twapDurationnumber––
twapIntervalSecondsnumber––

No output schema declared.

No examples provided.

create_agent_wallet ~72

Create a new Pear Protocol agent wallet for the authenticated user. The agent wallet is what Pear uses to sign Hyperliquid trades. After creation, the user MUST approve this wallet on Hyperliquid (the response message contains the approval instructions). WRITE: executes a state change. Requires PEAR_TRADE_ENABLED=true.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_account_summary ~51

Get the authenticated user's Pear Protocol account summary: agent wallet address, total closed trades, pending trigger-order USD value, pending TWAP-chunk USD value, and last sync timestamp. Requires PEAR_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_active_markets ~58

Get the most active Pear Protocol pair markets right now: current active pairs plus top gainers, top losers, highlighted pairs, and the user's watchlist. Use to see what's hot or as a starting point for narrowing into a specific pair.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_agent_wallet ~60

Get the authenticated user's Pear Protocol agent wallet address. The agent wallet is what Pear uses to sign Hyperliquid trades on the user's behalf. Returns an empty/missing address if no agent wallet has been created yet; call create_agent_wallet to create one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_health ~39

Check Pear Protocol API health. Returns service status, server timestamp, and uptime in seconds. Use this to verify the API is reachable before running other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_open_orders ~47

List the authenticated user's open limit, take-profit, and stop-loss orders on Pear Protocol. Returns each order's ID, type, status, and pair composition. Requires PEAR_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_open_positions ~48

List the authenticated user's currently open Pear Protocol pair positions, including position ID, entry ratio, mark ratio, unrealized PnL, and long/short composition. Requires PEAR_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pair_ratio ~106

Get the current ratio (long/short composition price) for a specific Pear Protocol pair. Pass long and short asset arrays. Returns the ratio, 24h change, and funding rate. Useful when you know the pair you care about and want the latest number.

NameTypeReqDescription
longAssetsarrayyesAsset symbols on the long side (e.g. ['BTC']).
shortAssetsarrayyesAsset symbols on the short side. Pass an empty array for long-only baskets.

No output schema declared.

No examples provided.

get_portfolio ~73

Fetch the authenticated user's full portfolio metrics on Pear Protocol: bucketed PnL across last 1 day / 1 week / 1 month / 1 year / all-time, plus overall stats (total trades, all-time volume, current open interest, unrealized PnL). Requires PEAR_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_trade_history ~113

Fetch the authenticated user's recent closed trades on Pear Protocol with realized PnL, entry/exit ratios, and pair composition. Optional date range and limit. Requires PEAR_API_KEY.

NameTypeReqDescription
endDatestring–ISO 8601 timestamp or epoch ms. Only return trades on or before this time.
limitinteger–Max number of trades to return. Default 50.
startDatestring–ISO 8601 timestamp or epoch ms. Only return trades on or after this time.

No output schema declared.

No examples provided.

get_twap_orders ~42

List the authenticated user's active TWAP (time-weighted average price) orders on Pear Protocol, including chunk execution and fill detail. Requires PEAR_API_KEY.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_markets ~202

Browse Pear Protocol pair markets with optional filters and pagination. Each market is a long/short composition with current ratio, 24h change, volume, open interest, and funding. Use to discover what's tradable, or with searchText to find a specific pair.

NameTypeReqDescription
change24hnumber–Minimum 24h ratio change (e.g. 0.05 for +5%).
enginestring–Filter by execution engine.
minVolumenumber–Minimum 24h volume in USD.
netFundingnumber–Filter by net funding rate.
pageinteger–Page number (1-indexed).
pageSizeinteger–Results per page. Default 20.
searchstring–Free-text search across market names (composition keys like `L:BTC|S:ETH`).
sortstring–Sort key (e.g. 'volume', 'change24h').

No output schema declared.

No examples provided.

open_position ~237

Open a new pair position on Pear Protocol. Specify executionType (MARKET / TRIGGER / TWAP / LADDER / TP / SL / SYNC), leverage (1-100), usdValue (≥1), slippage (0.001-0.1), and the long/short asset compositions (arrays of { asset, weight }). Optionally attach stopLoss/takeProfit and TWAP/TRIGGER/LADDER parameters. WRITE: executes a real trade. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
directionstring––
executionTypestringyes–
ladderConfigobject––
leverageintegeryes–
longAssetsarrayyes–
randomizeExecutionboolean––
referralCodestring––
shortAssetsarrayyes–
slippagenumberyes–
stopLoss–––
takeProfit–––
triggerTypestring––
triggerValuenumber––
twapDurationnumber––
twapIntervalSecondsnumber––
usdValuenumberyes–

No output schema declared.

No examples provided.

set_risk_parameters ~96

Set or update stop-loss / take-profit on an existing Pear Protocol position. Each threshold has type ('PRICE' or 'PERCENTAGE'), value, and optional trailing fields. Pass null to clear a field; omit it to leave unchanged. WRITE: changes risk parameters on a live position. Requires PEAR_TRADE_ENABLED=true.

NameTypeReqDescription
positionIdstringyes–
stopLoss–––
takeProfit–––

No output schema declared.

No examples provided.

Common questions

What is the io.github.MarvelNwachukwu/mcp-pear server?

io.github.MarvelNwachukwu/mcp-pear is listed in the public MCP registry as io.github.MarvelNwachukwu/mcp-pear. MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution. This page covers its npm package (@marvelcodes/mcp-pear).

Is the io.github.MarvelNwachukwu/mcp-pear server safe to use?

io.github.MarvelNwachukwu/mcp-pear scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.MarvelNwachukwu/mcp-pear server expose?

io.github.MarvelNwachukwu/mcp-pear exposes 20 tools: get_health, list_markets, get_active_markets, get_pair_ratio, get_account_summary, and 15 more. Their descriptions and schemas cost roughly 1,746 tokens of context every time the server is loaded.

Is the io.github.MarvelNwachukwu/mcp-pear server still maintained?

io.github.MarvelNwachukwu/mcp-pear is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.MarvelNwachukwu/mcp-pear server under?

io.github.MarvelNwachukwu/mcp-pear declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.