# io.github.HASAVAGE/teardrop (remote · api.teardrop.dev) Teardrop MCP gateway: paid tools for autonomous agents (x402, credits). - Trust score: 68/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-18 ## Components - remote · `api.teardrop.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/hasavage-teardrop/tools-mcp.md), [page](https://verifymcp.io/servers/hasavage-teardrop/tools-mcp) ## Channel facts - Endpoint: `https://api.teardrop.dev/tools/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-18. - **Endpoint Security**: 63/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 67/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 8494 tokens (~242/item across 35 items; 35 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 17/100 - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (97% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 35 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the io.github.HASAVAGE/teardrop MCP server? io.github.HASAVAGE/teardrop is a hosted endpoint at https://api.teardrop.dev/tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http hasavage-teardrop 'https://api.teardrop.dev/tools/mcp' ``` ### Cursor ```json { "mcpServers": { "hasavage-teardrop": { "url": "https://api.teardrop.dev/tools/mcp" } } } ``` ### VS Code ```json { "servers": { "hasavage-teardrop": { "type": "http", "url": "https://api.teardrop.dev/tools/mcp" } } } ``` ### Codex ```toml [mcp_servers.hasavage-teardrop] url = "https://api.teardrop.dev/tools/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "hasavage-teardrop": { "type": "remote", "url": "https://api.teardrop.dev/tools/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add hasavage-teardrop --url 'https://api.teardrop.dev/tools/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: hasavage-teardrop: url: "https://api.teardrop.dev/tools/mcp" ``` ### Netclaw ```json { "McpServers": { "hasavage-teardrop": { "Transport": "http", "Url": "https://api.teardrop.dev/tools/mcp" } } } ``` ### Vellum ```bash assistant mcp add hasavage-teardrop -t streamable-http -u 'https://api.teardrop.dev/tools/mcp' ``` ### Other ```json { "mcpServers": { "hasavage-teardrop": { "type": "http", "url": "https://api.teardrop.dev/tools/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-18 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-16 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-14 (score 66, +1) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-13 (score 65) First indexed and scored. ## MCP tools (35) ### `assess_counterparty_risk` (~186 tokens) Assess Counterparty Risk Return a decision-ready counterparty-risk verdict for an EVM address before funds or authority are committed. The result branches to high_risk, caution, acceptable, or insufficient_data with the evidence needed for the calling agent to act. Use when: Delegate this check before sending funds, granting approvals, or interacting with an unknown EVM address when the caller needs a bounded risk decision. Limitations: Analytics and heuristic risk assessment; not a credit bureau, fraud guarantee, or legal endorsement. Relies on DeBank indexing and on-chain Aave/Compound contract states. Alternatives: get_wallet_approvals, get_liquidation_risk, get_wallet_positions Input parameters: - `chain_ids` (array): DeBank chain identifiers scoping approvals and history; positions and net worth remain all-chain. - `wallet_address` (string, required): EVM wallet address (0x-prefixed) Output parameters: - `activity` - `approval_summary` - `as_of` (string) - `data_complete` (boolean) - `liquidation` - `partial_errors` (array) - `provenance` - `risk_factors` (array) - `total_net_worth_usd` - `verdict` (string) - `wallet_address` (string) ### `assess_market_resolution` (~255 tokens) Assess Market Resolution Return a decision-ready resolution-risk verdict for one Polymarket market before an agent trades, quotes, or forecasts it. The result branches to tradeable, ambiguous, avoid, or insufficient_data and names the resolution basis (price_feed, official_source, media_consensus, unspecified), UMA dispute state, rule-wording risks, and executability (liquidity, spread) so the calling agent can act without reading the full rules. Use when: Call once per market before placing, quoting, or forecasting a Polymarket position when the caller needs to know whether the rules and resolution state make the outcome well-defined. Repeat calls within two minutes return cached data. Limitations: Heuristic analysis of Polymarket rule wording and Gamma API state; not a probability forecast, legal advice, or a guarantee of how UMA voters resolve. Does not read order-book depth, event-level augmented negative-risk settings, or clarifications published off-platform. Alternatives: web_search, http_fetch Input parameters: - `market` (string, required): Polymarket market slug (e.g. 'will-bitcoin-reach-150k-in-2026'), numeric Gamma market id, or a polymarket.com market URL (the last path segment is used). Output parameters: - `as_of` (string) - `best_ask` - `best_bid` - `disputed` (boolean) - `end_date` - `hours_to_end` - `liquidity_usd` - `market_id` (string) - `neg_risk` (boolean) - `outcome_prices` (object) - `provenance` - `question` (string) - `resolution_basis` (string) - `resolution_source` (string) - `risk_factors` (array) - `rule_flags` (array) - `slug` (string) - `spread` - `uma_status` (string) - `verdict` (string) - `verdict_reason` (string) ### `calculate` (~201 tokens) Calculate Evaluate a safe arithmetic expression and return the numeric result. Supports +,-,*,/,**,%,sqrt,abs,round,floor,ceil,log,sin,cos,tan,pi,e. Use for derived figures (ratios, differences, percentages) that no tool output already provides. Use when: Use when an agent must derive a value that tool outputs do not already include, such as a ratio, spread, or percentage. Do not use to re-derive pre-computed fields like std_30d or dca_baseline_90d that get_token_price_historical returns. Limitations: Arithmetic only — no aggregation over tool history, no unit conversion, and no financial modeling beyond the listed functions. Errors return an error field rather than raising. Alternatives: get_token_price_historical, get_datetime Input parameters: - `expression` (string, required): A safe arithmetic expression, e.g. '(3 + 4) * 2 / sqrt(9)' Output parameters: - `error` - `expression` (string) - `result` ### `convert_currency` (~205 tokens) Convert Currency Convert an amount between fiat currencies (USD, EUR, GBP) and crypto assets (BTC, ETH, USDC, SOL) and return the converted amount plus the exchange rate used. Use when: Use when an amount must be expressed in a different currency than the source data — for example converting a USD portfolio value into EUR, or a fiat amount into its crypto equivalent. For prices only, get_token_price returns the rate directly without a second call. Limitations: Spot-rate conversion at request time; no historical or forward rates, and no slippage or fee modeling. Actual swap execution differs — use get_dex_quote for executable on-chain quotes. Alternatives: get_token_price, get_dex_quote Input parameters: - `amount` (number, required): Amount to convert - `from_currency` (string, required): Source currency (e.g. 'ETH', 'USD', 'BTC') - `to_currency` (string, required): Target currency (e.g. 'USD', 'EUR', 'BTC') Output parameters: - `amount` (number) - `converted_amount` (number) - `from_currency` (string) - `rate` (number) - `source` (string) - `to_currency` (string) ### `decode_transaction` (~206 tokens) Decode Transaction Decode a transaction's calldata into a human-readable function name and arguments, and return transaction status (1=success, 0=revert), gas used, and block number. Uses a supplied ABI when provided, otherwise 4byte.directory. Supports Ethereum mainnet and Base. Use when: Use when one known transaction must be explained — what function was called, with what arguments, and whether it succeeded. For wallet-wide activity patterns use get_wallet_history instead. Limitations: 4byte.directory matching can be ambiguous or absent for custom contracts; supply an ABI for precise decoding. One transaction per call; Ethereum mainnet and Base only. Alternatives: get_transaction, get_wallet_history Input parameters: - `abi_json`: Optional ABI JSON array for decoding. If omitted, 4byte.directory is used. - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `tx_hash` (string, required): Transaction hash (0x… 64 hex chars) Output parameters: - `block_number` - `chain_id` (integer) - `decode_source` - `decoded_args` - `from_address` (string) - `function_name` - `function_selector` - `gas_used` - `note` (string) - `raw_calldata` (string) - `status`: 1=success, 0=revert, None=pending - `to_address` - `tx_hash` (string) - `value_eth` (string) ### `delegate_to_agent` (~218 tokens) Delegate To Agent Delegate a task to a remote A2A-compliant agent: discover its capabilities via its agent card, send it a message, handle payment, and return the result. Use only when no local platform tool can fulfil the request. Use when: Use when a task requires specialist capabilities beyond the local tool set. Call discover_agents first when the remote agent URL is unknown. Do not retry unchanged after error_type=advertised_price_exceeds_cap; pick another result or adjust the cap. Limitations: Requires an allowlisted remote URL and sufficient delegation budget; the remote agent's price and capability claims are read from its card and are not independently verified. Involves real payment. Alternatives: discover_agents, web_search Input parameters: - `agent_url` (string, required): Base URL of the remote A2A agent (e.g. https://agent.example.com) - `task_description` (string, required): Natural language description of the task to delegate - `task_type` (string): Broad task class for routing telemetry; never include user data or task text. Output parameters: - `agent_name` (string): Name of the remote agent (from its agent card) - `cost_usdc` (integer): Cost of this delegation in atomic USDC - `error`: Error message, if any - `error_type`: Stable error type for delegation failures that require planner recovery. - `result` (string): Text result extracted from the remote agent's response - `status` (string): A2A task state: completed, failed, etc. ### `discover_agents` (~111 tokens) Discover Agents Find opt-in remote A2A agents, published tool capabilities, endpoints, and public reputation status. Use when: Use before delegate_to_agent when a specialist agent is needed but its URL is unknown. Limitations: Discovery is read-only and does not add an agent to the org allowlist; delegate_to_agent remains authoritative. Alternatives: delegate_to_agent Input parameters: - `limit` (integer): Maximum number of agents to return - `q`: Optional search across agent name, organization slug, or published tool name Output parameters: - `agents` (array) - `count` (integer) - `generated_at` - `registration_benefits_url`: Machine-readable registration benefits, requirements, and non-guarantees. - `registration_endpoint`: Endpoint where an organization can publish its own A2A endpoint. ### `get_datetime` (~147 tokens) Get Datetime Return the current UTC date and time as a formatted string and ISO 8601 timestamp, for grounding time-relative reasoning in the actual clock rather than training-data assumptions. Use when: Use when a task must anchor on the current date or time — computing ages, windows, deadlines, or 'as of today' context. The runtime context block already states the date, so call this only when a specific strftime format or a precise timestamp is needed. Limitations: UTC only — no timezone conversion. An unsupported strftime format silently falls back to the default format instead of erroring. Alternatives: calculate, get_block Input parameters: - `format` (string): strftime format string for the output Output parameters: - `datetime` (string) - `iso8601` (string) ### `get_block` (~182 tokens) Get Block Get block details (timestamp, gas used, base fee, miner, transaction count) for an Ethereum or Base block by number, hash, or 'latest'. Use to anchor events to a point in chain time. Use when: Use when a question depends on when a block occurred, how full it was, or its base fee — for example dating a transaction or checking congestion at a specific height. For current fee levels use get_gas_price instead. Limitations: One block per call; Ethereum mainnet and Base only. Historical base fee data depends on RPC node retention for older heights. Alternatives: get_transaction, get_gas_price Input parameters: - `block_identifier` (string): Block number, block hash, or 'latest'/'earliest'/'pending' - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) Output parameters: - `base_fee_gwei` - `gas_used` (integer) - `hash` (string) - `number` (integer) - `timestamp` (integer) - `transaction_count` (integer) ### `get_chain_metrics` (~237 tokens) Get Chain Metrics Compare blockchain ecosystem health via DeFiLlama: current TVL, 7/30-day TVL change, and aggregate fee activity. Pass chains such as ['Ethereum', 'Arbitrum', 'Solana'] for a focused comparison, or omit chains to inspect the highest-TVL ecosystems. Use when: Use for ecosystem-level comparisons — which chains are growing, where fee activity concentrates, or how a chain's TVL trended. For a single protocol's economics use get_protocol_tvl instead. Limitations: Third-party DeFiLlama analytics; historical and fee fields fail open (null) for uncovered chains. Not a real-time measure of chain throughput or security. Alternatives: get_protocol_tvl, get_dex_volume Input parameters: - `chains`: Optional chain names to compare, such as ['Ethereum', 'Arbitrum', 'Solana']. When omitted, return the highest-TVL chains up to limit. - `days` (integer): Lookback window used when selecting the historical TVL points to inspect. - `limit` (integer): Maximum number of chain rows to return when the result is not explicitly filtered. Output parameters: - `chains` (array) - `error` - `error_type` - `note` (string) - `provenance`: Source and freshness metadata for the DeFiLlama response. - `requested_chains` - `total_available` (integer) ### `get_dex_quote` (~469 tokens) Get Dex Quote Get the best Uniswap v3 swap quote on Ethereum (chain_id=1) or Base (chain_id=8453) via direct on-chain QuoterV2 calls. Queries all four fee tiers (100/500/3000/10000 bps) in parallel and returns the tier with the highest output amount, along with per-tier breakdown. Inputs are raw uint256 amounts and EIP-55 checksummed addresses; native ETH is not quoted directly — pass the WETH address. Returns no_liquidity=true when no pool exists for the pair. Point-in-time quote at the returned block_number; do not cache. Use when: Choose when you need a best-execution Uniswap v3 swap quote on Ethereum or Base before executing a trade — e.g. price impact, output amount, or route selection. Limitations: Quotes raw uint256 amounts with EIP-55 checksummed addresses only; native ETH is not quoted directly (pass WETH). Point-in-time at the returned block_number — do not cache. Alternatives: get_token_price, get_dex_volume Input parameters: - `amount_in` (string, required): Input amount in RAW uint256 units (e.g. '1000000' for 1 USDC, '1000000000000000000' for 1 WETH). Must be > 0 and < 2^128. Common token decimals: WETH/ETH/DAI/wstETH/cbETH/weETH 18, WBTC/cbBTC 8, USDC… - `chain_id` (integer): 1 = Ethereum mainnet, 8453 = Base mainnet. Other chains unsupported. - `token_in` (string, required): EIP-55 checksummed address of the token being sold. For native ETH, pass the WETH address (Ethereum: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2; Base: 0x4200000000000000000000000000000000000006). - `token_out` (string, required): EIP-55 checksummed address of the token being bought. Output parameters: - `amount_in` (string) - `amount_in_decimals` (integer) - `amount_out` (string) - `amount_out_decimals` (integer) - `amount_out_human` (string) - `block_number` (integer) - `chain_id` (integer) - `effective_rate` (string) - `fee_tier_used` - `no_liquidity` (boolean) - `quotes_per_tier` (array) - `token_in` (string) - `token_out` (string) ### `get_dex_volume` (~254 tokens) Get Dex Volume Compare decentralized exchange activity via DeFiLlama: 24h/7d/30-day volume, period-over-period changes, and each protocol's share of reported global 24-hour DEX volume. Filter by protocol and rank by a 1-, 7-, or 30-day lookback window. Use when: Use for landscape questions — which DEXs dominate volume, how activity shifted week-over-week, or a specific protocol's relative share. For executable swap pricing use get_dex_quote instead. Limitations: Third-party DeFiLlama reporting, not on-chain truth; coverage gaps understate smaller protocols. 24-hour share is computed against the unfiltered global total, so filtered results retain landscape context. Alternatives: get_dex_quote, get_chain_metrics Input parameters: - `limit` (integer): Maximum number of DEX protocols to return. - `lookback_days` (integer): Window used to rank the returned protocols: 1, 7, or 30 days (nearest supported window is used). - `protocols`: Optional protocol names or DeFiLlama slugs, such as ['uniswap-v3', 'curve-dex']. When omitted, return the largest DEX protocols. Output parameters: - `dexes` (array) - `error` - `error_type` - `note` (string) - `total_available` (integer) - `total_matching` (integer) - `volume_share_basis` (string) ### `get_defi_positions` (~267 tokens) Get Defi Positions Block-accurate DeFi positions for a wallet across Aave v3, Compound v3, Uniswap v3 LP, and Lido on Ethereum or Base. Returns Aave account health (collateral, debt, health factor, LTV) with per-reserve breakdown, Compound v3 market positions, Uniswap v3 LP positions by token ID, and on Ethereum the Lido stETH/wstETH balances with the current wstETH-to-stETH equivalent. Per-protocol failures are isolated — other protocols still return. Use when: Use when a block-accurate single-wallet protocol snapshot is needed, including health factor and LP position detail. For broad all-chain discovery or net worth across many protocols use get_wallet_positions instead. Limitations: On-chain RPC view of four protocol families on Ethereum and Base only; does not discover wallets' unknown or long-tail protocol positions. Compound v3 reports only a boolean liquidation flag — never state a numeric Compound health factor. Errors list which protocols were unavailable. Alternatives: get_wallet_positions, get_liquidation_risk, get_wallet_portfolio Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `wallet_address` (string, required): Wallet address (0x…) Output parameters: - `aave_v3` - `chain_id` (integer) - `compound_v3` (array) - `data_block_number` (integer) - `errors` (array) - `lido_staking` - `note` (string) - `uniswap_v3` (array) - `wallet_address` (string) ### `get_gas_price` (~226 tokens) Get Gas Price Get current EIP-1559 gas fees on Ethereum or Base: base fee, priority fee, next-block base fee estimate, and congestion (gas_used_ratio >0.5 busy, >0.9 very congested). Optional USD estimates cover a simple transfer and a swap-like transaction. Cached 10 seconds per chain. Use when: Use before advising a transaction — to time execution, size a gas budget, or judge congestion. Call once per decision; the 10-second cache makes rapid re-calls pointless. Limitations: Point-in-time estimate that changes every block; USD figures are rough heuristics at 21k/150k gas, not an execution quote. Ethereum mainnet and Base only. Alternatives: get_block, get_dex_quote Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `include_usd_estimate` (boolean): If true, include ETH spot price and rough USD cost estimates for a simple transfer (21k gas) and a swap-like transaction (150k gas). Output parameters: - `base_fee_gwei` - `chain_id` (integer) - `estimated_swap_cost_usd` - `estimated_transfer_cost_usd` - `eth_price_usd` - `gas_price_gwei` (string) - `gas_used_ratio` - `next_base_fee_gwei` - `priority_fee_gwei` ### `get_lending_rates` (~279 tokens) Get Lending Rates Get current on-chain lending supply/borrow APYs for Aave v3 reserves and Compound v3 markets on Ethereum or Base, with per-asset snapshots and Compound utilization. Use for protocol-specific yield comparisons such as USDC on Aave vs Compound. Use when: Use for protocol-specific lending-rate questions (e.g. 'Aave vs Compound USDC rates'). Prefer over get_yield_rates when the protocols are known; use get_yield_rates for broad pool discovery across many protocols. Do not fall back to web_search when this returns errors — report them. Limitations: On-chain snapshots of Aave v3 and Compound v3 on Ethereum and Base only; not a multi-protocol yield aggregator. Rates are point-in-time and change per block. Returns an errors list — report each unavailable protocol explicitly and treat empty rates with empty errors as transient RPC unavailability. Alternatives: get_yield_rates, get_defi_positions, get_liquidation_risk Input parameters: - `assets`: Optional asset-symbol filter (e.g., ['USDC','DAI']). Case-insensitive. Max 20 symbols. - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base). - `protocol` (string): Protocol to query: 'aave-v3', 'compound-v3', or 'all'. Output parameters: - `chain_id` (integer) - `data_block_number` (integer) - `errors` (array) - `note` (string) - `protocol` (string) - `rates` (array) ### `get_liquidation_risk` (~255 tokens) Get Liquidation Risk Assess DeFi liquidation risk for up to 50 wallets across Aave v3 and Compound v3 on Ethereum or Base. Returns per-wallet health factor, tiered risk classification (liquidatable, critical, warning, caution, healthy, no_debt), and an overall_tier aggregate. Per-protocol failures are isolated — one protocol's RPC error does not blank the other's result. Use when: Use for multi-wallet batch risk assessment (2+ wallets). For a single-wallet DeFi analysis use get_defi_positions, which already includes risk metrics. Use assess_counterparty_risk when the question is counterparty trust rather than position health. Limitations: View-only scan of Aave v3 and Compound v3 on Ethereum and Base with hardcoded market addresses; not a liquidation simulation or guarantee. Compound v3 exposes only a boolean liquidation flag — no numeric health factor. Duplicate wallet addresses are silently removed. Alternatives: get_defi_positions, assess_counterparty_risk, get_wallet_positions Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `wallet_addresses` (array, required): Wallet addresses to assess (max 50; duplicates are silently removed). Output parameters: - `chain_id` (integer) - `data_block_number` (integer) - `note` (string) - `results` (array) - `summary` ### `get_token_approvals` (~288 tokens) Get Token Approvals Block-accurate audit of ERC-20 allowances for a wallet across curated DeFi spenders (Uniswap, Aave, Compound, 1inch, 0x, OpenSea) on Ethereum or Base. Flags unlimited approvals by risk level (high=unknown spender, medium=trusted protocol, low=bounded). Use before swaps or after security incidents to detect active exploit vectors. Use when: Use for a free, block-accurate Ethereum/Base check of an address's exposure to the curated spender list. For broad all-chain spender discovery, hacked/abandoned flags, or NFT-adjacent exposure use get_wallet_approvals instead. Limitations: Covers only the tracked-asset registry and curated spenders — untracked tokens and custom spenders are excluded. Does not inspect NFT approvals or off-chain Permit2 sub-permits. An error field marks results as incomplete rather than clean. Alternatives: get_wallet_approvals, assess_counterparty_risk Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `spenders`: Spender contract addresses to check (max 20). Defaults to the curated DeFi protocol list. - `tokens`: Token contract addresses to check (max 50). Defaults to the platform tracked token list. - `wallet_address` (string, required): Wallet address (0x…) Output parameters: - `approvals` (array) - `chain_id` (integer) - `error` - `note` (string) - `risk_summary` - `wallet_address` (string) ### `get_wallet_approvals` (~206 tokens) Get Wallet Approvals Inspect a wallet's current ERC-20 token authorization exposure on one DeBank-supported chain. Returns discovered spenders, USD exposure, protocol attribution, and hacked or abandoned protocol flags. This is broader than the curated block-accurate get_token_approvals tool. Use when: Use when broad spender discovery or cross-chain security screening is needed. Call once per chain because DeBank requires a chain_id. Use get_token_approvals for a free, block-accurate Ethereum or Base scan of curated tokens and spenders. Limitations: The result is third-party analytics and may be stale. It covers token approvals only, not NFT approvals or off-chain Permit2 sub-permits; each chain consumes a separate billable provider call. Alternatives: get_token_approvals Input parameters: - `chain_id` (string, required): DeBank chain identifier, for example eth, arb, or base - `wallet_address` (string, required): EVM wallet address (0x-prefixed) Output parameters: - `approvals` (array) - `chain_id` (string) - `data_complete` (boolean) - `errors` (array) - `note` (string) - `provenance` - `wallet_address` (string) ### `get_token_price` (~238 tokens) Get Token Price Get current price, 24h change, market cap, FDV, and volume for one or more crypto tokens. Accepts ticker symbols, full names, or CoinGecko IDs; unknown symbols resolve automatically. Batch up to 50 tokens. Reuse price_usd/value_usd already returned by get_wallet_portfolio instead of re-calling. Use when: Use for spot pricing of named tokens — including batched multi-token queries. Do not call for tokens whose price get_wallet_portfolio already returned, or for address-only unknown tokens (report them as unrecognized). For historical windows use get_token_price_historical. Limitations: CoinGecko spot data; point-in-time and not an executable swap quote. Bare 0x addresses are not resolvable and should be treated as unknown tokens. Alternatives: get_token_price_historical, get_wallet_portfolio, get_dex_quote Input parameters: - `tokens` (array, required): Token symbols or CoinGecko IDs (e.g. ['BTC', 'ETH', 'SOL']) - `vs_currency` (string): Quote currency (usd, eur, gbp, btc, eth) Output parameters: - `prices` (array) - `vs_currency` (string) ### `get_protocol_tvl` (~411 tokens) Get Protocol Tvl Get Total Value Locked for one or many DeFi protocols from DeFiLlama: current USD TVL, 7/30-day change, fees and revenue when reported, per-chain breakdown, and optional daily historical series. Batch multiple protocols via protocols=[...] — batch responses return one compact economic summary per protocol; single-protocol calls add chain and historical detail. Supports 3,000+ protocols; use DeFiLlama slugs ('aave-v3', 'uniswap-v3'); common aliases are auto-corrected. Use when: Use for protocol-level economic questions — size, growth, fees, or revenue of a specific protocol. For 2+ protocols always batch in one call rather than calling per-protocol. Pass include_historical=true with days when a trend is needed; without it the response is a current TVL scalar. For ecosystem-level chain comparisons use get_chain_metrics instead. Limitations: Third-party DeFiLlama analytics, not on-chain truth. Upstream revenue failures surface as revenue_error_type and null economic fields are data gaps — never fabricate values for them. Alternatives: get_chain_metrics, get_yield_rates, get_dex_volume Input parameters: - `days` (integer): Lookback window in days for the historical series (only used when include_historical=True). - `include_historical` (boolean): If true, return a daily historical TVL series for the requested window. - `protocol`: DeFiLlama protocol slug (e.g. 'aave-v3', 'uniswap-v3', 'curve-dex'). Use lowercase with hyphens as shown on DeFiLlama. Tip: 'aave' works for the combined Aave TVL; 'aave-v3' for V3 only. Optional whe… - `protocols` (array): Optional batch mode: list of DeFiLlama protocol slugs. When provided, the tool returns one TVL result object per protocol. ### `get_token_price_historical` (~335 tokens) Get Token Price Historical Get historical crypto prices over a 1–365 day window: period statistics (start, end, % change, high, low), a downsampled daily series, high_30d, std_30d, and dca_baseline_90d. Use for period comparisons and trend analysis; prefer over web_search for time-comparative financial queries. Pass stats_only=true when the daily series is unnecessary. Use when: Use for time-comparative financial questions — month-over-month, YTD, volatility, or DCA baselines. Prefer over web_search for such queries. Use the pre-computed stats directly; do not re-derive them with calculate. Limitations: Daily granularity (downsampled), max 365-day window, CoinGecko coverage only. Check dca_baseline_90d_partial before relying on the baseline — incomplete history yields a partial baseline. Alternatives: get_token_price, web_search Input parameters: - `days` (integer): Lookback window in days (1–365). 1=5-min granularity, 2-90=hourly, 91+=daily. - `stats_only` (boolean): If true, omit the daily price series and return period stats plus precomputed 30-day high/volatility and 90-day DCA baseline metrics. - `tokens` (array, required): Token symbols or CoinGecko IDs (e.g. ['BTC', 'ETH']). Max 10 per call. - `vs_currency` (string): Quote currency (usd, eur, gbp, btc, eth). Lowercase 3–10 letters. Output parameters: - `days` (integer) - `tokens` (array) - `vs_currency` (string) ### `get_yield_rates` (~517 tokens) Get Yield Rates Get DeFi yield pool rates from DeFiLlama across 1,000+ protocols and all chains: pools sorted by APY with TVL, base/reward APY, and 7d/30d mean APY context, filterable by protocol, chain, min TVL, min/max APY, and symbol. Returns up to 50 pools. For protocol-specific lending comparisons (Aave vs Compound) prefer get_lending_rates. Use when: Use for broad cross-protocol yield discovery. Call at most once per request — filter with min_apy, max_apy, min_tvl_usd, and symbols_any in a single call, then sort client-side rather than re-calling. For protocol-specific rate questions use get_lending_rates. Limitations: Third-party DeFiLlama analytics; up to 50 pools per call. The `symbol` field lists underlying tokens (e.g. 'ETH-USDC') — filter client-side instead of re-calling with different arguments. Reward APY indicates reward-dependent yield; do not present spot APY as durable. Alternatives: get_lending_rates, get_protocol_tvl, get_token_price Input parameters: - `chain`: Filter by chain name (e.g. 'Ethereum', 'Base', 'Arbitrum'). Case-insensitive. None = all chains. - `limit` (integer): Maximum number of pools to return, sorted by APY descending. - `max_apy`: Exclude pools with APY above this value (%). Default None = no upper bound. Use to filter out leveraged/boosted pools (e.g. max_apy=30) so genuine stablecoin yields surface. - `min_apy` (number): Exclude pools with APY below this value (%). Default 0 includes all. - `min_tvl_usd` (number): Exclude pools with TVL below this threshold (USD). Default $1M filters noise. - `protocols`: Filter by DeFiLlama project slugs (e.g. ['aave-v3', 'compound-v3']). None or empty list = include all protocols. - `stable_only` (boolean): When true, return only stablecoin pools and rank by 30d mean APY first to emphasize consistency over short-term spikes. - `symbols_any`: Optional symbol filter. If provided, include pools whose symbol field contains at least one token from this list (case-insensitive). Use held token symbols from get_wallet_portfolio to focus results. Output parameters: - `filters_applied` (object) - `note` (string) - `pools` (array) - `provenance`: Source and freshness metadata for the DeFiLlama response. - `total_matching` (integer) ### `web_search` (~224 tokens) Web Search Real-time web search via Tavily for current events, fact-checking, and research. Use search_depth='advanced' for complex queries (higher quality, higher cost) and topic='news' or 'finance' for headlines or market information. Use when: Choose when the task needs current, external, or factual information not available from on-chain or local data — e.g. news, prices, documentation, or fact-checking. Limitations: Returns web snippets, not raw page bodies; results depend on Tavily coverage. Advanced depth costs more. Not a substitute for on-chain tools like get_token_price. Alternatives: get_token_price, http_fetch Input parameters: - `num_results` (integer): Number of web search results to return (1–20, default 5). - `query` (string, required): Search query - `search_depth` (string): 'basic' for fast results, 'advanced' for thorough research (higher cost) - `topic` (string): Search topic: 'general' for web, 'news' for headlines, 'finance' for markets Output parameters: - `note` - `num_results` (integer) - `query` (string) - `results` (array) ### `count_text_stats` (~124 tokens) Count Text Stats Return word, character, sentence, and paragraph counts plus average words per sentence for a given text, for length checks and content sizing decisions. Use when: Use when output length must be validated or reported — e.g. verifying a summary meets a length contract or comparing document sizes. Do not use for semantic summarization; it counts only. Limitations: Pure counting on the provided text — no language detection, no reading-level or sentiment analysis, and no retrieval of external content. Alternatives: web_search, http_fetch Input parameters: - `text` (string, required): Text to summarize Output parameters: - `average_words_per_sentence` (number) - `character_count` (integer) - `paragraph_count` (integer) - `sentence_count` (integer) - `word_count` (integer) ### `http_fetch` (~172 tokens) Http Fetch Fetch a web page and return its main text content, cleaned of markup. Use to read articles, documentation, and other resources referenced by URL. Blocks private and cloud-metadata addresses and re-validates every redirect hop. Use when: Use when a known URL's content is needed and structured tools cannot answer — e.g. reading a linked document or API docs. For general factual lookup prefer web_search; for token prices prefer get_token_price. Limitations: Read-only GET-style extraction returning cleaned text, not raw HTML or binary content. JS-heavy pages may yield little content; private/internal network targets are deliberately unreachable. Alternatives: web_search, get_token_price Input parameters: - `max_chars` (integer): Maximum characters of extracted content to return - `url` (string, required): URL to fetch (http or https only) Output parameters: - `content` (string) - `content_length` (integer) - `title` - `truncated` (boolean) - `url` (string) ### `get_eth_balance` (~178 tokens) Get Eth Balance Get the exact on-chain native ETH balance of an address on Ethereum or Base, in wei and ether. get_wallet_portfolio already includes native ETH in its holdings — call this only for a standalone balance without a portfolio scan. Use when: Use when a wallet's gas-availability or standalone ETH amount must be verified block-accurately. Do not call after or alongside get_wallet_portfolio — the holdings list already includes native ETH. Limitations: Native ETH only; ERC-20 balances require get_erc20_balance. Requires an EIP-55 checksummed address. Ethereum mainnet and Base only. Alternatives: get_wallet_portfolio, get_erc20_balance Input parameters: - `address` (string, required): Ethereum address (0x…) - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) Output parameters: - `address` (string) - `balance_eth` (string) - `balance_wei` (string) - `chain_id` (integer) ### `get_erc20_balance` (~194 tokens) Get Erc20 Balance Get the exact on-chain ERC-20 balance of a wallet for one token contract, normalized by decimals and returned with the token's symbol. Use for a precise single-token check. Use when: Use when a specific token contract's balance must be verified block-accurately — e.g. confirming funds before an approval or transfer. For a multi-asset portfolio view use get_wallet_portfolio instead. Limitations: One token contract per call on Ethereum or Base; the contract address is required, so unknown tokens cannot be looked up by symbol. Returns raw balance data only — no USD valuation. Alternatives: get_wallet_portfolio, get_eth_balance Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `token_address` (string, required): ERC-20 token contract address (0x…) - `wallet_address` (string, required): Wallet address (0x…) Output parameters: - `balance_formatted` (string) - `balance_raw` (string) - `chain_id` (integer) - `token_address` (string) - `token_decimals` (integer) - `token_symbol` (string) - `wallet_address` (string) ### `get_transaction` (~178 tokens) Get Transaction Get details and receipt for one Ethereum or Base transaction by hash: bounded calldata, normalized event logs, transaction index, and receipt-derived effective gas price and fee when available. Use to verify a specific transaction's status and outcome. Use when: Use when one known transaction must be verified — status, logs, gas paid, or execution outcome. To understand what the calldata means use decode_transaction; for wallet-wide activity use get_wallet_history. Limitations: One transaction hash per call on Ethereum or Base; pending transactions may not resolve yet. Calldata is returned bounded, not decoded — use decode_transaction for semantic decoding. Alternatives: decode_transaction, get_block, get_wallet_history Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `tx_hash` (string, required): Transaction hash (0x…) Output parameters: - `block_number` - `chain_id` (integer) - `effective_gas_price_gwei` - `fee_eth` - `fee_wei` - `from_address` (string) - `gas_price_gwei` - `gas_used` - `input_data`: Hex calldata, bounded to 8 KiB - `input_data_truncated` (boolean) - `logs` (array) - `logs_truncated` (boolean) - `status`: 1=success, 0=revert, None=pending - `to_address` - `transaction_index` - `tx_hash` (string) - `value_eth` (string) ### `get_wallet_portfolio` (~205 tokens) Get Wallet Portfolio Get aggregated token holdings with USD values for a wallet address. Tracks 19 major assets on Ethereum and 12 on Base, including spot, lending, liquid-staking, restaking, and stablecoin assets. Sorted by USD value. Returns up to 20 holdings. Includes native ETH balance in the holdings list — calling get_eth_balance separately after this is redundant. Use when: Choose when you need a wallet's overall token exposure and USD value on Ethereum or Base in one call. Call once per chain for a cross-chain comparison. Limitations: Tracks a fixed set of major assets per chain, not arbitrary tokens. Returns up to 20 holdings. Native ETH is included, so calling get_eth_balance separately is redundant. Alternatives: get_eth_balance, get_token_price, get_defi_positions Input parameters: - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `wallet_address` (string, required): Wallet address (0x…) Output parameters: - `chain_id` (integer) - `fetch_errors` (array) - `holdings` (array) - `note` (string) - `total_value_usd` (number) - `wallet_address` (string) ### `get_wallet_history` (~232 tokens) Get Wallet History Get one page of decoded transaction history for an EVM wallet across DeBank-supported chains. Returns send, receive, and approval categories with protocol, token, exchange, gas, and USD metadata. Use the returned next_cursor as start_time to page backward. Use when: Use for wallet activity discovery, protocol interaction history, exchange exposure, and gas analysis. Page backward with next_cursor for older activity. Use get_transaction or decode_transaction when one known transaction needs block-level details. Limitations: DeBank returns at most 20 entries per call and the data may be stale. This tool is not a complete ledger, PnL engine, or cost-basis calculator because historical execution prices and all transfer semantics are not guaranteed. Alternatives: get_transaction, decode_transaction Input parameters: - `chain_ids`: Optional DeBank chain identifiers; omit to query all supported chains. - `page_count` (integer): Number of history entries to request (maximum 20). - `start_time`: Return entries earlier than this Unix timestamp for cursor pagination. - `wallet_address` (string, required): EVM wallet address (0x-prefixed) Output parameters: - `cex_dict` (object) - `chain_ids` - `data_complete` (boolean) - `errors` (array) - `has_more` (boolean) - `history_list` (array) - `next_cursor` - `note` (string) - `page_count` (integer) - `project_dict` (object) - `provenance` - `start_time` - `token_dict` (object) - `wallet_address` (string) ### `get_wallet_positions` (~389 tokens) Get Wallet Positions Get a wallet's DeFi positions across all DeBank-supported chains and protocols. Returns protocol-level positions, asset/debt/net USD values, optional token lists, aggregate exposure, and optional all-chain net worth. Set include_token_balances=true to also return DeBank's complete cross-chain wallet token list. Set include_token_lists=false for a compact balance and debt summary without nested position tokens. This covers substantially more protocols and chains than the block-accurate get_defi_positions tool. Use raw-RPC tools for liquidation, swap quotes, or other transaction-critical questions. Use when: Use for broad wallet discovery, portfolio allocation, protocol exposure, or cross-chain position questions. Set include_token_balances=true when complete wallet token discovery is required; otherwise the response only includes tokens attached to protocol positions. Set include_token_lists=false when only protocol balances, debt, or aggregate exposure are needed. Use get_defi_positions when the user needs a block-accurate Aave, Compound, Uniswap, or Lido snapshot. Limitations: DeBank portfolio data is third-party analytics and may be stale, including occasional long refresh delays. It is read-only, EVM wallet oriented, and does not prove current liquidation or execution state. include_token_balances adds a separate billable DeBank request; include_token_lists only changes response detail. Alternatives: get_defi_positions, get_wallet_portfolio, get_token_approvals Input parameters: - `include_net_worth` (boolean): Include all-chain net worth and per-chain balances; disable to avoid that additional provider request. - `include_token_balances` (boolean): Include DeBank's complete cross-chain token balance list; adds a billable provider request. - `include_token_lists` (boolean): Include protocol position token lists; disable for a compact balance and debt summary. - `wallet_address` (string, required): EVM wallet address (0x…) Output parameters: - `chain_balances` (array) - `data_complete` (boolean) - `errors` (array) - `include_net_worth` (boolean) - `include_token_balances` (boolean) - `include_token_lists` (boolean) - `note` (string) - `positions` (array) - `provenance` - `staleness_seconds`: Max age in seconds of the underlying DeBank position data (from per-item update_at), or None when unavailable. - `token_balances` (array) - `total_asset_usd` - `total_debt_usd` - `total_net_usd` - `total_net_worth_usd` - `wallet_address` (string) ### `read_contract` (~371 tokens) Read Contract Call any view/pure function on a smart contract and return the decoded result, using a supplied ABI fragment. Supports historical reads via block_identifier and caller_address context for msg.sender-dependent views. Read-only: state-changing functions are rejected. Use when: Use when a protocol question needs a contract read that no higher-level tool covers — e.g. a niche view function or a protocol outside the standard tool set. Prefer purpose-built tools (get_defi_positions, get_lending_rates) for supported protocols. Limitations: Requires a valid ABI fragment; payable/nonpayable functions are rejected. Ethereum mainnet and Base only, with bounded RPC timeout and retry. Alternatives: get_defi_positions, get_lending_rates, get_token_approvals Input parameters: - `abi_fragment` (string, required): JSON array containing the ABI for the function to call. Supports both modern (stateMutability: view/pure) and legacy (constant: true) formats. Only read-only functions are allowed. - `args` (array): DEPRECATED: Positional arguments for the function call. Use 'args_json' for complex objects or Gemini compatibility. - `args_json`: Optional JSON array string of positional arguments for the function call. Use this instead of 'args' for complex types or when calling via Google/Gemini. - `block_identifier` (string): Block number, block hash, or 'latest'/'earliest'/'pending' - `caller_address`: Optional EVM address to supply as msg.sender for caller-dependent view functions. This does not sign or submit a transaction. - `chain_id` (integer): Chain ID (1=Ethereum, 8453=Base) - `contract_address` (string, required): Contract address (0x…) - `function_name` (string, required): Name of the function to call Output parameters: - `block_identifier` (string) - `caller_address` - `chain_id` (integer) - `contract_address` (string) - `function_name` (string) - `result` ### `record_predictions` (~126 tokens) Record Predictions Record a complete structured prediction document for downstream evaluation. Call once with the exact machine-readable prediction; the human-readable report is provided separately. Use when: Use at the end of a scheduled analysis run to persist the machine-readable prediction for later scoring. Call exactly once with the complete prediction document — never partially or repeatedly. Limitations: Internal sink for scheduled analysis, not a caller-facing marketplace tool. Stores the prediction as given; no validation of prediction quality or deduplication across calls. Alternatives: get_datetime Input parameters: - `predictions` (object, required): The complete structured prediction document for this run. Output parameters: - `recorded` (boolean) ### `resolve_ens` (~188 tokens) Resolve Ens Resolve an ENS name (e.g. 'vitalik.eth') to an Ethereum address, or an address to its primary ENS name, with avatar text record when available. Mainnet only. Use when: Use only when no 0x address is available and a name must become an address (or vice versa for attribution). If a 0x address is already present in the task or session, use it directly — resolution is redundant and adds latency. Limitations: Ethereum mainnet ENS only — no other chains or naming services. Reverse records are optional on ENS, so a valid address may legitimately have no primary name. Alternatives: get_wallet_portfolio, get_wallet_history Input parameters: - `name` (string, required): ENS name (e.g. 'vitalik.eth') to resolve to an address, or an Ethereum address (0x…) for reverse lookup to a primary ENS name. Output parameters: - `address` - `avatar` - `error` - `name` - `resolved` (boolean) ### `validate_opportunity` (~185 tokens) Validate Opportunity Return a decision-ready yield-opportunity verdict before capital is deployed. The result branches to sustainable, caution, unsustainable, or insufficient_data and gives the calling agent the evidence needed to proceed, pause, or reject the opportunity. Use when: Delegate this check before deploying capital into a DeFi yield pool or staking opportunity when the caller needs an independent sustainability and liquidity decision. Limitations: Heuristic economic assessment based on DeFiLlama analytics and CoinGecko pricing. Does not audit smart contract bytecode, protocol governance, or admin key security. Alternatives: get_yield_rates, get_protocol_tvl, get_lending_rates, assess_counterparty_risk Input parameters: - `pool_id` (string, required): DeFiLlama yield pool UUID (e.g. '747c1d2a-c668-4682-b9f9-296708a3dd90'). Output parameters: - `as_of` (string) - `chain` (string) - `data_complete` (boolean) - `liquidity_summary` - `partial_errors` (array) - `pool_id` (string) - `project` (string) - `provenance` - `risk_factors` (array) - `sustainability_reason` (string) - `symbol` (string) - `verdict` (string) - `yield_summary` ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/hasavage-teardrop/tools-mcp#diagnostics ## Score history - 2026-10-18: 68 - 2026-10-17: 67 - 2026-10-16: 67 - 2026-10-15: 66 - 2026-10-14: 66 - 2026-10-13: 65 ## Common questions ### What is the io.github.HASAVAGE/teardrop MCP server? io.github.HASAVAGE/teardrop is an MCP server listed in the public MCP registry as io.github.HASAVAGE/teardrop. Teardrop MCP gateway: paid tools for autonomous agents (x402, credits). This page covers its hosted endpoint (https://api.teardrop.dev/tools/mcp). ### Is the io.github.HASAVAGE/teardrop MCP server safe to use? io.github.HASAVAGE/teardrop scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the io.github.HASAVAGE/teardrop MCP server expose? io.github.HASAVAGE/teardrop exposes 35 tools: assess_counterparty_risk, assess_market_resolution, calculate, convert_currency, decode_transaction, and 30 more. Their descriptions and schemas cost roughly 8,459 tokens of context every time the server is loaded. ### Does the io.github.HASAVAGE/teardrop MCP server require authentication? No. We connected to io.github.HASAVAGE/teardrop without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the io.github.HASAVAGE/teardrop MCP server still maintained? io.github.HASAVAGE/teardrop is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://api.teardrop.dev/tools/mcp - Repository: https://github.com/teardrop-ai/teardrop - Changelog RSS feed: https://verifymcp.io/servers/hasavage-teardrop/tools-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/hasavage-teardrop/tools-mcp.json - HTML version of this page: https://verifymcp.io/servers/hasavage-teardrop/tools-mcp