Home / MCP registry index / io.github.HASAVAGE/teardrop

io.github.HASAVAGE/teardrop

io.github.HASAVAGE/teardrop in the official MCP registry. Endpoint https://api.teardrop.dev/tools/mcp. Source: github.com/teardrop-ai/teardrop.

The registry describes it as: Teardrop MCP gateway: paid tools for autonomous agents (x402, credits).

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http teardrop https://api.teardrop.dev/tools/mcp

{
  "mcpServers": {
    "teardrop": {
      "url": "https://api.teardrop.dev/tools/mcp"
    }
  }
}

code --add-mcp '{"name":"teardrop","type":"http","url":"https://api.teardrop.dev/tools/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

assess_counterparty_risk assess_market_resolution calculate convert_currency decode_transaction delegate_to_agent discover_agents get_datetime get_block get_chain_metrics get_dex_quote get_dex_volume get_defi_positions get_gas_price get_lending_rates get_liquidation_risk get_token_approvals get_wallet_approvals get_token_price get_protocol_tvl get_token_price_historical get_yield_rates web_search count_text_stats http_fetch get_eth_balance get_erc20_balance get_transaction get_wallet_portfolio get_wallet_history get_wallet_positions read_contract record_predictions resolve_ens validate_opportunity

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-hasavage-teardrop/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-hasavage-teardrop)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers