Skip to main content
Glama

pigi.finance — DeFi Vault Intelligence

Server Details

DeFi vault data from pigi.finance: yields, TVL, history and risk ratings across chains.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
pigi-fi/pigi-mcp
GitHub Stars
0
Server Listing
Pigi Finance — DeFi Vault Intelligence
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation4/5

Most tools target distinct concepts (hacks, rates, usage, protocol ratings, vaults), and the vault trio (get_vault / get_vault_history / get_vault_stats) is separated by snapshot vs time-series vs aggregate. The main friction is that get_vault takes a pool id while get_vault_history/get_vault_stats take strategy_id, and get_protocol vs list_protocols differ mainly in scope — descriptions warn about both, but the id duality is a genuine trap.

Naming Consistency5/5

Every tool follows a clean get_/list_ verb_noun pattern (get_hacks, get_protocol, list_vaults, get_vault_stats, etc.) with no camelCase mixing or vague standalone verbs. The scheme is predictable and signals read-only access consistently.

Tool Count5/5

Nine tools is well-scoped for a read-only DeFi intelligence API: four lookup/aggregate endpoints, three vault views, plus rates and usage. Each tool earns its place with no redundant thin wrappers.

Completeness4/5

The surface covers the core lifecycle a read-only data client needs: discovery (list_vaults, list_protocols), detail (get_vault, get_protocol), history/stats, plus rates and hack context. Minor gaps remain — no explicit way to resolve a vault's pool id vs strategy_id, and no cross-vault comparison or portfolio view — but agents can work around these.

Available Tools

9 tools
get_hacksAInspect

DeFi hack / exploit loss events, plus a reference set of major TradFi banking losses (the dataset behind pigi.finance/hacks). Each event has a date, the protocol or institution, the USD amount lost, and — for DeFi — a type saying what kind of protocol was hit. The summary in the response totals the ENTIRE filtered set (count + total_amount_hacked + date range), so for "how much was lost in X" read summary rather than paging through every event.

Inputs: to, from, sort, type, +4 more.

get_protocolAInspect

One protocol node's cumulative rating (same formula as list_protocols) with the vaults that counted: each with its published score and band, TVL, and the share of the vault term it carried, largest first (long lists are truncated; items_total says how many there were). Custom-plan callers also get the node's rubric lines (audit & bounty, admin authority, pause authority, operational history, scale). A node id that is not a rated protocol (e.g. a curator) is an error — take ids from list_protocols.

Inputs: node_id (required), chain_id.

get_ratesAInspect

DeFi Base Rate (stablecoin + ETH vault-set mean yield) and the 3-month U.S. T-Bill risk-free rate. Returns the most recent ~30 daily points of each series.

Inputs: no named parameters.

get_usageAInspect

Your API request usage for the current calendar month (UTC) and your plan limit.

Inputs: no named parameters.

get_vaultAInspect

Get a single vault by its pool id (the id field from list_vaults).

Inputs: id (required).

get_vault_historyAInspect

Daily time-series (TVL, APR, APY, risk-adjusted APR = APR minus a penalty from the vault's published 0-100 risk score, 30-day moving averages) for a vault. Use the strategy_id from list_vaults (NOT the pool id).

Inputs: strategy_id (required), range.

get_vault_statsAInspect

Aggregated stats over fixed windows (weekly/monthly/quarterly/yearly): TVL low/high, APR, APY, and inflows (net TVL change over the window; positive = net inflow, negative = net outflow — a TVL-based figure that also reflects yield earned, not just deposits/withdrawals). Use the strategy_id from list_vaults. Omit period to get all windows.

Inputs: strategy_id (required), period.

list_protocolsAInspect

pigi's cumulative protocol rating for every rated protocol node, in one call: score = 0.6 × the node's own rating + 0.4 × the TVL-weighted mean of the published scores of the vaults that deposit into it (weights fixed by pigi; with no rated vault the node rating stands alone). Band A (safest) .. F from fixed thresholds, score 0-100 higher = safer. Node ids look like aave-v3-ethereum, euler-v2, morpho-blue-ethereum, metamorpho-v1-1, sparklend, uniswap-v3 — use them with get_protocol. chain_id narrows which vaults count, not the protocol term; framework-wide nodes (euler-v2, uniswap-v3) mix chains without it.

Inputs: chain_id.

list_vaultsAInspect

List DeFi vaults pigi.finance tracks (across Aave, Morpho, Euler, Uniswap, and more). Each vault carries pigi's published risk rating where assessed: risk_band (A safest .. F), risk_score (0-100, higher = safer) and risk_adjusted_apr (APR minus the score-derived penalty). Filter server-side by asset_class / search (e.g. "USDC") / risk_band / min_risk_score and sort by apr, tvl, risk_score or risk_adjusted_apr, so "best low-risk USDC vault" is one call. Returns a compact page — narrow with filters and paginate; this is not the full dataset. Use the returned strategy_id with get_vault_history / get_vault_stats, and id with get_vault.

Inputs: sort, limit, offset, search, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.