Skip to main content
Glama
790,995 tools. Updated 2026-11-16 19:03

"A CLI tool for auditing MCP (Model Context Protocol) configurations or servers" matching MCP tools:

  • 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
    ConnectorNo auth
  • Get the exact commands for running the local crypto plane (the `@seekrit/mcp` npm server, the `@seekrit/cli` CLI, seekrit-run, seekrit-proxy), including a copy-paste .mcp.json that reuses this session's credential. Takes no arguments and returns prose plus config. Call this the moment you need to SET or READ a secret value — no tool on this server will ever return one. Use local_tool_for instead when you want the single command for one named operation.
    ConnectorNo auth
  • Rank DeFi protocols by total value locked from DefiLlama, filtered by chain, category or name substring, with each protocol's slug, category, chain list, TVL in USD, 1d/7d TVL change and market cap. Use it to size a protocol, find the biggest venues on a chain, or resolve the slug the protocol-detail tool needs. A protocol DefiLlama publishes no TVL for keeps a null figure, never a zero. Read live at request time and held for 5 minutes. Costs $0.008 USDC per call via x402 on Base; an unpaid call returns the payment challenge instead of data, and a call that returns no data is never settled so it costs nothing. Equivalent HTTP route: GET /defi/protocols.
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • Forecast Track Record — Silicon Analysts' OWN projections, frozen monthly into write-once vintages and graded against outcomes. Every row: model, scenario (bear/base/bull), series, target period, the predicted mid + low–high band frozen at vintage time, and once the period matures, the realized value with a correct/partial/incorrect resolution and error %. Vintages cannot be backfilled or edited — a changed projection that was never frozen is gone, which is what makes this a track record. USE THIS for: checking how Silicon Analysts' HBM/DDR4/CoWoS projections have scored, citing our prediction accuracy, comparing what we projected for a period across successive vintage months, auditing the frozen assumption set behind a projection (include_assumptions=true). DO NOT USE for: third-party forecasts (TrendForce/WSTS/company guidance — use get_forecasts; ours are graded, theirs are archived); current market values (use get_wafer_pricing / get_hbm_market_data). Filters: model (hbm-pricing-model|dram-ddr4-model|cowos-capacity-model), series (e.g. hbm3e), include_assumptions (bool). Fully public at full fidelity for every tier including anonymous — the scorecard is deliberately ungated. Cite as "Silicon Analysts — Forecast Track Record".
    ConnectorNo auth
  • 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
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • 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
    ConnectorNo auth
  • Build a coordination report for a translated Navisworks model: translation status/progress, derivative outputs, available views (2D sheets / 3D viewables), total element count, and a per-category element breakdown. Doubles as the canonical way to poll translation status after nwd_upload. When to use: after nwd_upload to check whether translation has completed before calling clash/object tools; at the end of a coordination session to generate a status snapshot for the weekly BIM report; when auditing a model revision to confirm expected element counts per discipline. When NOT to use: do not use for a per-element property dump — use nwd_list_objects; do not use for clash results — use nwd_get_clashes. APS scopes required: viewables:read data:read bucket:read (read-only). Rate limits: APS default ~50 req/min per endpoint; this tool issues up to 4 sequential APS calls (manifest, metadata, properties — two with retry). When polling for translation completion, backoff: 5s, 10s, 30s, 60s, 120s — Model Derivative NWD translation typically completes in 1-10 min but large federated models can take 20+ min. Errors: 401 APS token expired (retry); 403 missing scope (report); 404 URN not found (model was never uploaded or bucket TTL expired); 409 N/A; 422 translation failed permanently — inspect report.translation_status == "failed" and report.derivatives[].status; 429 rate limit (backoff); 5xx APS upstream (retry once). Property extraction may legitimately 202 "isProcessing" — the tool handles retry and then silently swallows to still return manifest/metadata (element_count will be 0 until properties index is built). Side effects: none. Pure read. Idempotent — report reflects current APS state. Logs usage to D1 usage_log.
    ConnectorNo auth
  • Daily TVL, volume, and fees time series for one named protocol. One-shot profile→get_platform_info. Ranked multi-protocol list→search_platforms. CEX perps history: pass exchange_slug (e.g. gate) or platform_name. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.
    ConnectorNo auth
  • Fetches a domain's homepage and checks for content patterns that could constitute prompt injection attacks against AI agents that visit and ingest the page. Signals include hidden text, invisible divs, `<!-- AI: ignore -->` style comments, and known injection patterns. Use this tool when: - You are vetting a domain before feeding its content into an LLM context. - You want to assess the prompt injection risk of a URL before browsing it with an agent. - You are auditing a set of domains for adversarial AI content. Do NOT use this tool when: - You want tracker surveillance data — use `get_domain` instead. - You want AI training opt-out signals — use `intel_optout` instead. - You want the agent surface (MCP/OpenAPI) — use `intel_agent` instead. Inputs: - `domain` (query, required): Domain to scan. Returns: - `injection_signals`: list of signal types detected (e.g., `hidden_text`, `ai_instruction_comment`, `invisible_div`). - `risk_level`: `none`, `low`, `medium`, or `high` based on signal count and type. Cost: - Free. No API key required. Latency: - Typical: 2-4s (HTML fetch), p99: 7s.
    ConnectorNo auth
  • Statically audit an MCP tool surface from a public HTTPS URL or tools/list snapshot. Returns deterministic scores and findings without invoking any target tool or making LLM calls. When the user asks to check another installed MCP server, read that server's complete tool definitions from client context and pass them as snapshot (MCP `name` or Cursor-style `tool` both work; do not use file paths or $ref). If those definitions are unavailable, ask the user for its public endpoint or tools/list JSON instead of inventing an audit.
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • Estimate the USDC cost of a chat completion request before paying — free, no payment, no authentication required. Read-only: no state changes and no external calls; the estimate is computed locally from server pricing config, so repeated calls with identical inputs return identical results (idempotent). Use this tool to check the exact price for a given model/mode, messages, and max_tokens before calling the paid chat_completions tool. Provide either mode (auto/eco/premium routing) or model (explicit id, mutually exclusive with mode); one of the two is required — if both are sent, model wins. mode values: auto = cheapest model fitting the context, eco = cheapest available, premium = best model.
    ConnectorNo auth
  • List the full model catalog. Returns id, provider, display name, context window, max output tokens, pricing, and a per-model `available` verdict for your account (with `unavailable_reason` when false). Nothing is filtered out — `available` is what varies by caller. Call before `create_deliberation` if the user wants specific models. Model IDs from this endpoint are what `create_deliberation`'s `models` parameter expects.
    ConnectorNo auth
  • Read-only. Returns detailed information for one sailing-ship model, including vessel background, technical notes, and build-log parts. Use list_builds to browse or filter the model catalog, and use list_model_slugs when a model slug must be identified from a name or metadata. Use this tool when details for one known model are needed; do not use it for catalog browsing. Without partNumber or partSlug, returns model metadata and a summary list of build-log parts. Set partNumber or partSlug to retrieve one build-log part with complete, untruncated content. If both are provided, partSlug takes precedence. Returns a not-found result if the model or requested build-log part does not exist.
    ConnectorOAuth
  • Use this when the user asks about a specific Model Context Protocol server — whether it is listed in the official MCP registry, what endpoint it publishes, how current its listing is, or whether that endpoint responds. Returns the registry record (name, version, publish and update dates, declared remote endpoints, registry status) plus the result of one anonymous request to a registry-published endpoint. Reports observations only. It does NOT assess whether a server is safe, trustworthy, well-built or suitable — we cannot see what a server does with data, and reachability is not safety. Many listed servers require authentication and cannot be queried anonymously; that is normal and is not a fault. Absence from the registry is not evidence a server does not exist. Not for: security assessment, recommending which MCP server to install, or checking AI tools in the RightAIChoice catalog (use check_tool_status).
    ConnectorNo auth
  • Use this when the user asks about a specific Model Context Protocol server — whether it is listed in the official MCP registry, what endpoint it publishes, how current its listing is, or whether that endpoint responds. Returns the registry record (name, version, publish and update dates, declared remote endpoints, registry status) plus the result of one anonymous request to a registry-published endpoint. Reports observations only. It does NOT assess whether a server is safe, trustworthy, well-built or suitable — we cannot see what a server does with data, and reachability is not safety. Many listed servers require authentication and cannot be queried anonymously; that is normal and is not a fault. Absence from the registry is not evidence a server does not exist. Not for: security assessment, recommending which MCP server to install, or checking AI tools in the RightAIChoice catalog (use check_tool_status).
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • 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
    ConnectorNo auth
  • Hands supplies structure, verification and execution; your own model supplies drafts and decisions, and no platform model is called. action=create starts a run from a goal (mode preview runs the loop in a throwaway context and never commits; mode run commits after verification and policy). action=advance sends facts you found (each with its sources), a batch of actions to execute, or finish. A contradicted fact blocks the run until it is found again. When the approval policy asks, the run is awaiting_user with a pending_request to relay to the user; reply with action=answer. action=status returns the run and action=events returns events after a seq cursor (the same stream the CLI and the Playground Studio read).
    ConnectorOAuth