Possible integration: AlgoVault composite verdicts as a --signal-source for perp arb exec

[AlgoVaultFi]

Hey hypurrquant team — kudos on perp-cli. The CLI + MCP combo, the agent-first design, the HIP-3/HIP-4 coverage, the shipped pace (86 versions in 60 days) — it's the cleanest "AI agent ↔ on-chain DEX perps" execution layer on npm right now.

Reaching out from AlgoVault Labs — we run api.algovault.com/mcp, an MCP server that returns composite trading verdicts (signal/confidence/regime) for AI agents. Different lane from perp-cli: you're the hands; we're the brain. We don't execute, we don't custody, we don't compete on plumbing.

The asymmetric idea:

Add a --signal-source <provider> flag to perp arb exec (or perp strategy run, wherever it fits) that lets users plug in a third-party signal provider before execution. e.g.:

perp arb exec ETH HL BINANCE 1000 --signal-source algovault
# perp-cli queries algovault.com/mcp for the composite verdict
# → only executes if AlgoVault confidence > threshold
# → respects perp-cli's existing risk/dry-run/idempotency layers

No exclusivity, no commitment from your side — just an open hook. Other providers (or users' own MCP servers) could fill the same flag.

Why we think it's interesting for perp-cli users:

• Composite verdict layered on top of your raw arb_scan rates → fewer false-positive entries
• Live, on-chain-verified track record — currently 90.0% PFE WR across 74,733 trade calls, 26 Merkle batches anchored on Base L2 (algovault.com/track-record)
• Free tier (100 calls/mo) for testing → no signup required for x402 micropay tier
• All 5 exchanges your CLI supports + crypto + TradFi (Hyperliquid stocks/indices/commodities)

What we'd offer:

• Reference impl + integration tutorial (we already ship these for Binance, OKX, Bybit, Bitget — happy to add a perp-cli one for the AlgoVault skills repo)
• Pre-tagged crypto-quant-signal-mcp@^1.10.7 with stable response shape — no breaking changes to the response surface
• Cross-link from our /integrations page once landed

What we'd ask:

Just the --signal-source flag (plus an HTTP-based provider interface so any MCP server fills it, not just us). If users actually use it, we'd love to talk about deeper integration — referral economics, co-marketing, joint Skills bundle. If they don't, no harm done.

Happy to PR the AlgoVault provider implementation if the flag lands. Open to whatever shape makes sense for perp-cli — issue, ADR, prototype, whatever.

— AlgoVault Labs · api.algovault.com/mcp · github.com/AlgoVaultLabs