Skip to main content

perquants-mcp

MCP connector for perquants — specialized Hyperliquid derivatives data for AI agents, pay-per-call over x402 (USDC on Base). No account, no API key — your agent pays a few cents per call from its own wallet.

Tools:

Tool Returns Price
get_hip3_decision(dex, asset) Pre-trade risk gate — verdict (tradeable/caution/avoid), cost to execute, score + sub-components, funding, basis, OI-vs-cap, risk flags ~$0.05
get_hip3_preview(dex, asset) Verdict band + one-line reason (a cheap first check) free
get_hip3_health(dex, asset) HIP-3 market health: oracle deviation, liquidity, OI vs cap, flags, 0–100 score ~$0.02
get_funding(coin) Funding rate: latest, annualized, 24h/7d means, sign streaks ~$0.01
get_basis(coin) Spot-perp premium (basis) in bps + means, streaks, churn ~$0.01

get_hip3_decision is the primary tool — call it before trading or sizing a HIP-3 builder market (tokenized stocks, commodities, forex, pre-IPO). It's the one decision-ready call no free API packages. Methodology is public: https://api.perquants.com/api/v1/methodology.

Install

uvx perquants-mcp          # run with no install
# or
pip install perquants-mcp

Configure your wallet

Paid calls are settled on Base mainnet in USDC, so the connector needs a wallet private key with a little USDC (and a few cents of ETH for nothing — x402 settlement is gasless for the buyer). Use a dedicated, low-balance wallet, never your main one.

export PERQUANTS_BUYER_KEY=0x<private key of a Base wallet funded with USDC>

Without PERQUANTS_BUYER_KEY, the tools return a clear "payment required" error.

Use in Claude Desktop / Cursor

Add to your MCP config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "perquants": {
      "command": "uvx",
      "args": ["perquants-mcp"],
      "env": { "PERQUANTS_BUYER_KEY": "0x<your Base wallet private key>" }
    }
  }
}

Then ask your agent things like "what's the funding on HYPE?" or "is the xyz:NVDA HIP-3 market healthy?" and it calls the tools (paying per call).

Use from Python

from perquants_mcp import PerquantsClient

client = PerquantsClient(buyer_key="0x...")   # omit to only read free/402 responses
print(client.get_json("/api/v1/hip3/xyz/NVDA"))

How it works

The connector is a thin client: it GETs the hosted perquants API, and on a 402 Payment Required it signs an x402 USDC payment with your wallet and retries. It holds no funds and runs locally — your key never leaves your machine.

Returns data/metrics, not financial advice.

License

MIT — see LICENSE.

Metadata

Release files for perquants-mcp 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for perquants-mcp 0.1.1
File Size Uploaded Provenance Actions
perquants_mcp-0.1.1.tar.gz 6.2 kB Without provenance Details for perquants_mcp-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for perquants-mcp 0.1.1
File Interpreter ABI Platform Actions
perquants_mcp-0.1.1-py3-none-any.whl Python 3 none any Details for perquants_mcp-0.1.1-py3-none-any.whl

Total release size: 13.5 kB

Release files / perquants_mcp-0.1.1.tar.gz

Download URL perquants_mcp-0.1.1.tar.gz
Size 6.2 kB
Tags Source
SHA-256 checksum
How to use checksums
736cbb5e0098de6535ec5fb09832a20bc1c7b630b934aff322b23bf40a525c03
BLAKE2b-256 checksum
How to use checksums
4fa22584837beda1daea82cc5f377c76c8fd21dad0a8e3ac27196ba53caa3f27
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / perquants_mcp-0.1.1-py3-none-any.whl

Download URL perquants_mcp-0.1.1-py3-none-any.whl
Size 7.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
92aed4dee6d889ccea0b4b2079ad0889f2cd9390c1bc52204eca9f9b69447b49
BLAKE2b-256 checksum
How to use checksums
1f746cc798e9529650da76b33c8f1a5300d862b3029a7e6123fb457c500c0639
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for perquants-mcp 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page