Home / MCP registry index / io.github.parkyucheol-del/alphapipeline

io.github.parkyucheol-del/alphapipeline

io.github.parkyucheol-del/alphapipeline in the official MCP registry. Endpoint https://alphapipeline-eu.onrender.com/mcp. Source: github.com/parkyucheol-del/alphapipeline.

The registry describes it as: Pay-per-call x402 API for AI trading agents: pre-trade security checks, Polymarket & HIP-4 odds.

We read its 30 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http alphapipeline https://alphapipeline-eu.onrender.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "alphapipeline": {
      "url": "https://alphapipeline-eu.onrender.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"alphapipeline","type":"http","url":"https://alphapipeline-eu.onrender.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

market.kimchi_alert tools.ai_markdown security.token_risk security.contract_health_audit security.token_prescreen security.token_authenticity security.token_diagnostic derivatives.funding_rate derivatives.funding_rate_value derivatives.funding_apr_matrix dex.liquidity_slippage arb.spread_matrix derivatives.whale_position_audit calendar.macro_dday prediction.neg_risk_arbitrage prediction.exit_capacity_audit prediction.order_split_guide prediction.bid_ask_spread_pct prediction.orderbook_imbalance_ratio prediction.liquidity_depth_after_haircut prediction.polymarket_fee_estimate prediction.polymarket_mispricing prediction.hip4_snapshot prediction.hip4_price_ladder prediction.hip4_price prediction.hip4_mispricing market.cycle_compare market.oracle_gap market.oracle_gap_bp unlocks.dump_risk

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-parkyucheol-del-alphapipeline/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-parkyucheol-del-alphapipeline)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Crypto and Web3 MCP servers · Finance and markets MCP servers · Security MCP servers