_ registry / mcp http-sse · checked 47m ago

envelop-lp-insight

https://unisafe.envelop.is

Registry code: 4bf4b02a17265f4f

api record

envelop-lp-insight 0.3.0 — read-only history and analytics for Envelop unisafe Uniswap v4 LP managers: what a position has earned since it opened, who a manager's operators are, which of its pools pays best and whether moving is worth it. Holds no keys and cannot sign.

Not here: allocate, recenter, move, claim, reinvest — anything that becomes a transaction. Those are the local `envelop-mcp-lp` server's (it holds the operator key and re-derives every number you pass it before signing) or the owner's own, in the app at https://unisafe.envelop.is. A suggestion from here is numbers, never…

endpoint
https://unisafe.envelop.is/mcp
protocol
http-sse ·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 envelop-lp-insight live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is envelop-lp-insight free to use?
Yes — the hub reached it with no key and no payment.
What tools does envelop-lp-insight have?
4 tools: suggest_move, get_position_history, list_operators, rank_pools.
Is envelop-lp-insight 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
408ms

last good check

priced tools
0

of 4 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • suggest_move unknown never probed

    Compares the position's current pool against the rest of the manager's set and, when the gap is worth it, returns the numbers for a move: destination pool, ticks, and how much liquidity. It returns NUMBERS, never calldata — pass them to the local envelop-mcp-lp server's propose_move, which re-derives each one against chain state and puts it through the policy and the price-oracle guard before anything is signed. The full ranking and the caveats come back with every answer so the suggestion can be disagreed with.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "chainId",
        "manager",
        "salt"
      ],
      "properties": {
        "salt": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$",
          "description": "Position key"
        },
        "chainId": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "EVM chain id, e.g. 42161 for Arbitrum One",
          "exclusiveMinimum": 0
        },
        "manager": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "Manager NFT contract address"
        },
        "minGainPct": {
          "type": "number",
          "minimum": 0,
          "description": "Minimum APR advantage, in percentage points, before moving is suggested. Default 1."
        }
      }
    }
    arguments 32 lines
  • get_position_history unknown 47m ago

    Every position of a manager, or one position by salt: when it opened, its pool, its lifetime fees and its events. Answered from the index, falling back to the Envelop history API and then to a log scan; the answer says which one served it and how current that source is.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "chainId",
        "manager"
      ],
      "properties": {
        "salt": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{64}$",
          "description": "Position key"
        },
        "chainId": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "EVM chain id, e.g. 42161 for Arbitrum One",
          "exclusiveMinimum": 0
        },
        "manager": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "Manager NFT contract address"
        }
      }
    }
    arguments 26 lines
  • list_operators unknown 47m ago

    Addresses currently authorised to rebalance a manager's positions. They can never withdraw — that is enforced by the contract. On the scan path the answer may be `partial`, which means a revoked operator could still be listed; from the index it never is.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "chainId",
        "manager"
      ],
      "properties": {
        "chainId": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "EVM chain id, e.g. 42161 for Arbitrum One",
          "exclusiveMinimum": 0
        },
        "manager": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "Manager NFT contract address"
        }
      }
    }
    arguments 21 lines
  • rank_pools unknown 47m ago

    Fee APR over the last complete day for each pool this manager is configured with, best first. Only the manager's own pools are candidates: a move can target a pool only if the owner fixed it into the set when the manager was created. Pools that could not be scored are listed separately with the reason — a pool missing from the ranking is not a bad pool.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "chainId",
        "manager"
      ],
      "properties": {
        "chainId": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "EVM chain id, e.g. 42161 for Arbitrum One",
          "exclusiveMinimum": 0
        },
        "manager": {
          "type": "string",
          "pattern": "^0x[0-9a-fA-F]{40}$",
          "description": "Manager NFT contract address"
        }
      }
    }
    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 4bf4b02a17265f4f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4bf4b02a17265f4f/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/4bf4b02a17265f4f/badge.svg)](https://brick.blue/agent/4bf4b02a17265f4f?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
80%

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.