Home / MCP registry index / io.github.SajanMelcher/plumbline-mcp

The Spice Melange Trading Desk: DeepBook market data connector

io.github.SajanMelcher/plumbline-mcp in the official MCP registry. Endpoint https://plumbline-mcp.fly.dev/mcp. Source: github.com/SajanMelcher/plumbline-mcp.

The registry describes it as: A Mentat's eye on Sui DeepBook v3: read-only market data plus desk template tools. No keys.

We read its 31 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 plumbline-mcp https://plumbline-mcp.fly.dev/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "plumbline-mcp": {
      "url": "https://plumbline-mcp.fly.dev/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"plumbline-mcp","type":"http","url":"https://plumbline-mcp.fly.dev/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_pools get_mid_price get_order_book get_volume get_pool_params get_recent_trades get_ohlcv get_indexer_status get_bm_fills get_swing_range get_pool_stats estimate_fees list_templates create_template_order check_template_order get_desk_rhythm wallet_setup_guide get_swap_quote build_swap_tx check_holder golden_path_market_read build_create_balance_manager_tx build_bm_deposit_tx build_bm_withdraw_tx build_limit_order_tx build_cancel_order_tx get_book_depth get_cetus_pool walrus_store_guide build_walrus_register_tx read_walrus_blob

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-sajanmelcher-plumbline-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-sajanmelcher-plumbline-mcp)

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.

Related

Finance and markets MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
Simpler.Asia
asia.simpler/simpler-asia
200 tools, nothing matched
2026-10-26
ai.firmbrain/x402-services
ai.firmbrain/x402-services
159 tools, nothing matched
2026-10-21
EventTrader MCP
com.cymetica/event-trader-mcp
152 tools, nothing matched
2026-10-27
MORVS
io.github.morvs-ai/morvs
145 tools, nothing matched
2026-10-27
com.calcfleet/calculators
com.calcfleet/calculators
122 tools, nothing matched
2026-10-26