_ registry / mcp http-sse · checked 3h ago

renzo

https://mcp.renzoprotocol.com

Registry code: 005382422d7a4052

api record

MCP server for Renzo protocol data, including chains, vaults, operators, and ezETH metrics.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.renzoprotocol.com/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 renzo live?
No — it has stopped answering the hub's checks (checked 3h ago). It answered 82% of checks over the last 30 days.
Is renzo free to use?
Yes — the hub reached it with no key and no payment.
What tools does renzo have?
9 tools: get_withdrawal_requests, get_token_balances, get_vault_details, get_vault_strategy, get_ezeth_info, get_protocol_stats, get_operators, get_supported_chains, ….
Is renzo 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
retired
uptime, 30 days
82.4%

90 days 88.3%· all time 88.3%

latency
452ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 428 checks · signed record
  • down → retired· fetch failed
  • degraded → down· fetch failed
  • live → degraded· fetch failed
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain trading & defi
used for
  • get ezeth apr and tvl
  • list restaking vaults
  • check renzo token balances for an address
  • get pending withdrawal requests
takes → gives
text → data
tools
9 reads
_ 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 9 tools
5 open 4 never probed 5 of 9 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.

  • get_ezeth_info reads open 8d ago

    Get current ezETH metrics: APR, total supply, TVL, price, and exchange rate

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_protocol_stats reads open 8d ago

    Get aggregate Renzo protocol statistics: total TVL, per-ecosystem TVL, APRs, and supported chain count

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_operators reads open 8d ago

    List Renzo protocol operators, optionally filtered by product (ezETH, pzETH, ezSOL, etc.)

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "product": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • get_supported_chains reads open 8d ago

    List all blockchain networks Renzo operates on, including supported products per chain

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_vaults reads open 8d ago

    List Renzo vaults with current TVL and APR, optionally filtered by ecosystem (eigenlayer, symbiotic, jito, generic)

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "ecosystem": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • get_withdrawal_requests reads unknown never probed

    Get a user's pending ezETH withdrawal requests from the WithdrawQueue contract, including amounts, claimability status, and time remaining. Pass an Ethereum address.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$"
    }
  }
}
    arguments 13 lines
  • get_token_balances reads unknown 8d ago

    Get a user's Renzo token balances on Ethereum mainnet (ezETH, pzETH, vault LP tokens) with ETH and USD values. Pass an Ethereum address.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$"
    }
  }
}
    arguments 13 lines
  • get_vault_details reads unknown 7d ago

    Get detailed information for a specific Renzo vault, including daily TVL snapshots, operators, and strategy parameters (current LTV, target LTV, max LTV) for reserve vaults. Pass a vault address or symbol (e.g. 'ezREZ', 'ezCompETH1').

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId"
  ],
  "properties": {
    "vaultId": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • get_vault_strategy reads unknown 7d ago

    Get the strategy and AVS (Actively Validated Service) allocations for an EigenLayer vault. Shows where the vault's capital is deployed, how much is staked in each AVS, and which operators run the infrastructure. Supports ezETH, ezEIGEN, and ezREZ.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vaultId"
  ],
  "properties": {
    "vaultId": {
      "type": "string"
    }
  }
}
    arguments 12 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 005382422d7a4052.

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