_ registry / mcp streamable-http · checked 1h ago

lpsignal

https://api.lpsignal.app

Registry code: 626dd6235cf897ce

api record

LPSignal ranks concentrated-liquidity LP opportunities (Uniswap v3/v4, PancakeSwap v3, Aerodrome/Velodrome Slipstream on Ethereum, BNB Chain, Base, Arbitrum, Optimism, Polygon, Robinhood Chain) by NET APR = fees earned by a specific price range minus its impermanent loss, from hourly backtests on exact on-chain fees.

- Percentages are annualised (APR) and come from backtests of past data: history, not a forecast or financial advice.

endpoint
https://api.lpsignal.app/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lpsignal live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is lpsignal free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does lpsignal have?
8 tools: find_pair_pools, get_pool, backtest_range, list_signals, signal_track_record, smart_lp_leaderboard, list_pools, my_account.
Is lpsignal safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
601ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open1 auth-required 5 never probed 3 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • smart_lp_leaderboard open 1h ago

    Wallets ranked by what their closed LP positions made versus simply holding the tokens. Without a Pro key: the top 10, addresses masked.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "chain": {
      "enum": [
        "ethereum",
        "bsc",
        "base",
        "arbitrum",
        "optimism",
        "polygon",
        "robinhood"
      ],
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "default 10"
    },
    "windowDays": {
      "enum": [
        30,
        90
      ],
      "type": "integer"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • list_pools open 1h ago

    Active pools ranked by the net APR (fees − impermanent loss) of their best price range over a window (default 7 days), with that range's ticks, TVL, 24h volume and the pool-level fee APR DEX sites show. Filter by chain and pool class.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "sort": {
      "enum": [
        "netApr",
        "feeApr",
        "ilApr",
        "inRange",
        "tvl",
        "volume24h",
        "fees24h",
        "poolApr"
      ],
      "type": "string",
      "description": "default netApr"
    },
    "chain": {
      "enum": [
        "ethereum",
        "bsc",
        "base",
        "arbitrum",
        "optimism",
        "polygon",
        "robinhood"
      ],
      "type": "string"
    },
    "class": {
      "enum": [
        "stable",
        "correlated",
        "volatile"
      ],
      "type": "string",
      "description": "stable = stablecoin pairs, correlated = e.g. ETH/stETH, volatile = everything else"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "default 10"
    },
    "order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string"
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "window": {
      "enum": [
        1,
        24,
        168,
        720
      ],
      "type": "integer",
      "description": "backtest window in hours (default 168 = 7 days)"
    },
    "minTvlUsd": {
      "type": "number",
      "description": "default 10000"
    }
  },
  "additionalProperties": false
}
    arguments 73 lines
  • my_account auth-required 1h ago

    With an API key: the account's plan, the signal kinds pushed to it, and its custom alert rules.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • find_pair_pools unknown never probed

    Every listed pool of a token pair across chains, DEXes and fee tiers (TVL ≥ $10k), each with its best range by 7-day net APR, best first. Symbols are matched case-insensitively, in either order.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tokenA",
    "tokenB"
  ],
  "properties": {
    "chain": {
      "enum": [
        "ethereum",
        "bsc",
        "base",
        "arbitrum",
        "optimism",
        "polygon",
        "robinhood"
      ],
      "type": "string"
    },
    "tokenA": {
      "type": "string",
      "description": "e.g. USDC"
    },
    "tokenB": {
      "type": "string",
      "description": "e.g. WETH"
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • get_pool unknown never probed

    A pool's details and its backtest of every range it is evaluated on (fee APR, impermanent loss, net APR, time in range, the exact ticks) over 1 hour, 24 hours, 7 days and 30 days.

    mcp-tool

    {
  "type": "object",
  "required": [
    "chain",
    "address"
  ],
  "properties": {
    "chain": {
      "enum": [
        "ethereum",
        "bsc",
        "base",
        "arbitrum",
        "optimism",
        "polygon",
        "robinhood"
      ],
      "type": "string"
    },
    "address": {
      "type": "string",
      "description": "pool contract address (0x + 40 hex), or a Uniswap v4 pool id (0x + 64 hex)"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • backtest_range unknown never probed

    Backtest a symmetric range of ±rangePct% around the price at the window's start (0 = full range) on a pool over the last `days` days: fee APR, impermanent loss, net APR, time in range, the ticks.

    mcp-tool

    {
  "type": "object",
  "required": [
    "chain",
    "address",
    "rangePct"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "default 7"
    },
    "chain": {
      "enum": [
        "ethereum",
        "bsc",
        "base",
        "arbitrum",
        "optimism",
        "polygon",
        "robinhood"
      ],
      "type": "string"
    },
    "address": {
      "type": "string",
      "description": "pool contract address (0x + 40 hex), or a Uniswap v4 pool id (0x + 64 hex)"
    },
    "rangePct": {
      "type": "number",
      "maximum": 50,
      "minimum": 0,
      "description": "half-width in percent; 0 = full range"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • list_signals unknown never probed

    The newest signals: opportunities (net_apr: a range paying a high net APR over 7 days and still today; burst: the last hour; hot_pool: a big pool's fee APR jumping) and risk alerts (depeg, tvl_outflow), with the exact ticks and, once scored, the realised outcome. Without a paid key opportunities appear 24 hours after they fired.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "kinds": {
      "type": "array",
      "items": {
        "enum": [
          "net_apr",
          "burst",
          "hot_pool",
          "tvl_outflow",
          "depeg",
          "smart_lp"
        ],
        "type": "string"
      }
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "default 10"
    },
    "before": {
      "type": "string",
      "description": "page: signals with an id below this"
    },
    "source": {
      "enum": [
        "default",
        "rules",
        "subscribed"
      ],
      "type": "string",
      "description": "with a key: rules = your custom-rule matches, subscribed = what your push channels deliver"
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • signal_track_record unknown never probed

    How past opportunity signals really did: each is backtested again on its exact ticks after the fact (7 days for net_apr, 24 hours for burst). Counts, share positive, median APR at the signal vs realised, the worst.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 365,
      "minimum": 7,
      "description": "signals fired in the last N days (default 30)"
    },
    "kind": {
      "enum": [
        "net_apr",
        "burst"
      ],
      "type": "string",
      "description": "default net_apr"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 626dd6235cf897ce.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/626dd6235cf897ce/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/626dd6235cf897ce/badge.svg)](https://brick.blue/agent/626dd6235cf897ce?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.