"Setting up an MCP server in Kubernetes" matching MCP tools:

• shillbot_claim_task

  Swarm Tips — Aggregated AI Agent Activities

  [STATE] Claim a Shillbot task. Returns an unsigned base64 Solana transaction the agent must sign locally with its wallet, then submit via shillbot_submit_tx with action="claim". Non-custodial — the MCP server never sees your private key. Requires a registered wallet (call register_wallet first).

  Connector

• tronsave_get_internal_account

  TronSave MCP Server

  Retrieve the Tronsave internal account profile for the current logged-in session (wallet/represent address, balances, deposit address). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Use when the user needs their linked address or balance. Read-only; does not submit orders or change chain state.

  Connector

• strale_ping

  Strale - 290+ API capabilities for AI agents

  Checks that the Strale API is reachable and the MCP server is running. Call this before a series of capability executions to verify connectivity, or when troubleshooting connection issues. Returns server status, version, tool count, capability count, solution count, and a timestamp. No API key required.

  Connector

• platform_tool_finder

  Inferventis MCP Server

  Discovers the most relevant tools available on this MCP server for a given task using local semantic search (MiniLM-L6-v2 embeddings). Accepts a plain-English description of what needs to be accomplished and returns the best matching tools ranked by relevance, along with their input schemas, pricing tier, and exact call instructions. Use this tool first when you are connected to this server but do not know which specific tool to call — describe your goal and let platform_tool_finder identify the right capability. Do not use this tool if you already know the tool name — call that tool directly instead. Returns up to 10 results ranked by semantic similarity score.

  Connector

• search_mcp_servers

  Swarm Tips — Aggregated AI Agent Activities

  [READ] Search the Layer 3 curated directory of MCP servers and agent-work tools. The directory has 30 entries across three vetting tiers — `first-party` (operated by the swarm.tips DAO), `vetted` (third-party, we've used + verified), `discovered` (cataloged from public sources, not yet exercised). Filter by `query` (substring vs name/description/tags), `category` (substring), and `tier`. Results sort first-party → vetted → discovered. The same directory powers swarm.tips/discover; this tool exposes it programmatically. Use this when an agent needs to find an MCP server for a capability (DeFi, search, browser automation, etc.) instead of an opportunity (which `discover_opportunities` covers).

  Connector

• switch_dannet_server

  dannet

  Switch between local and remote DanNet servers on the fly. This tool allows you to change the DanNet server endpoint during runtime without restarting the MCP server. Useful for switching between development (local) and production (remote) servers. Args: server: Server to switch to. Options: - "local": Use localhost:3456 (development server) - "remote": Use wordnet.dk (production server) - Custom URL: Any valid URL starting with http:// or https:// Returns: Dict with status information: - status: "success" or "error" - message: Description of the operation - previous_url: The URL that was previously active - current_url: The URL that is now active Example: # Switch to local development server result = switch_dannet_server("local") # Switch to production server result = switch_dannet_server("remote") # Switch to custom server result = switch_dannet_server("https://my-custom-dannet.example.com")

  Connector

• baselight_ping

  Baselight

  Simple ping test to verify MCP server is responding

  Connector

• tronsave_internal_create_extend_request

  Tronsave MCP Testnet

  Submit an extension request for existing delegated resources on TronSave via authenticated REST `POST /v2/extend-request`. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Side effect: creates an extension order and may commit TRX from the internal account. `extendData` must follow the REST contract (see schema on each row). Populate it from TronSave outside this MCP—for example the authenticated `POST /v2/get-extendable-delegates` response field `extendData`, or another TronSave client. Do not copy rows blindly from `tronsave_list_extendable_delegates` (GraphQL); that payload shape differs and is for market discovery only.

  Connector

• tronsave_get_deposit_address

  TronSave MCP Server

  Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.

  Connector

• vf_health

  VoiceFlip

  Returns VoiceFlip MCP server health and version metadata. No authentication required. Use this first to verify the server is reachable from your MCP client.

  Connector

• lz_list_chains

  Tenzro LayerZero V2 MCP

  List all 16 chains supported by this LayerZero MCP server with their Endpoint IDs (EIDs). Includes Ethereum, Arbitrum, Optimism, Polygon, BSC, Avalanche, Base, Solana, zkSync, Sei, Sonic, Berachain, Story, Monad, MegaETH, and Tron. EIDs are used in EndpointV2.quote() and EndpointV2.send() to identify destination chains.

  Connector

• get_legal_documents

  Molt2Meet

  Get all active legal documents an agent must accept on registration. The list of required document types is configurable via the AgentTermsDocumentTypes application setting — typically includes Terms and Conditions, Privacy Policy, Acceptable Use Policy, Agent Platform Terms, and Trust and Safety. Each document includes its type reference, name, version, effective date, and full markdown content. Call this before register_agent so you know what the agent is accepting when setting acceptedTerms=true. No authentication required.

  Connector

• tronsave_get_user_info

  Tronsave MCP Testnet

  Get the current authenticated user's profile and account settings. Requires a valid signature session from `tronsave_login` and `mcp-session-id` in request headers. Wallet signing always happens client-side; never send private keys to the server.

  Connector

• frogeye_batch_scan

  Frogeye Security Scanner

  Batch scan up to 10 code snippets in a single MCP call. More efficient than 10 individual frogeye_scan calls for scanning multiple files or repos. Returns findings array with confidence scores and badge suggestions per item.

  Connector

• platform_tool_finder

  Inferventis — Financial Data, News & Web MCP

  Discovers the most relevant tools available on this MCP server for a given task using local semantic search (MiniLM-L6-v2 embeddings). Accepts a plain-English description of what needs to be accomplished and returns the best matching tools ranked by relevance, along with their input schemas, pricing tier, and exact call instructions. Use this tool first when you are connected to this server but do not know which specific tool to call — describe your goal and let platform_tool_finder identify the right capability. Do not use this tool if you already know the tool name — call that tool directly instead. Returns up to 10 results ranked by semantic similarity score.

  Connector

• tronsave_login

  Tronsave MCP Testnet

  Create an authenticated server session and return a `sessionId` for subsequent tool calls. Default mode is wallet signature login for platform tools; secondary mode is `apiKey` login for internal tools. For wallet login, ALWAYS call `tronsave_get_sign_message` first, sign that exact message client-side, then call `tronsave_login` with `signature_timestamp` in exact format `<signature>_<timestamp>` (signature and timestamp joined by `_`). Use returned `sessionId` as `mcp-session-id` on every subsequent request.

  Connector

• tronsave_get_deposit_address

  Tronsave MCP Testnet

  Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.

  Connector

• ping

  nara-tour

  Connectivity check — returns server version and current timestamp. Use to verify MCP server is reachable before calling other tools.

  Connector

• status

  Quotewise

  Check server connectivity, authentication status, and database size. When to use: First tool call to verify MCP connection and auth state before collection operations. Examples: - `status()` - check if server is operational, see quote_count, and current auth state

  Connector

• createDeepResearch

  Parallel Task MCP

  Creates a Deep Research task for comprehensive, single-topic research with citations. USE THIS for analyst-grade reports, NOT for batch data enrichment. Use Parallel Search MCP for quick lookups. After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed. Multi-turn research: The response includes an interaction_id. To ask follow-up questions that build on prior research, pass that interaction_id as previous_interaction_id in a new call. The follow-up run inherits accumulated context, so queries like "How does this compare to X?" work without restating the original topic. Note: the first run must be completed before the follow-up can use its context.

  Connector