Verify that the FXMacroData API and MCP server are reachable.

Get usage statistics for this MCP server session. Returns tool call counts, success rates, and average latency.

Bridge an A2A (Agent-to-Agent Protocol) task to an MCP server. Extracts the intent from the A2A task, maps it to an MCP tool, calls the tool, and wraps the result in A2A response format. Use this to let A2A agents interact with any MCP server. Requires authentication.

Upload a file to the Compoid MCP server. Accepts a data URI (data:<mime>;base64,<data>). Returns the server-side path to use as file_upload in Compoid_create_record or Compoid_update_record.

List sites in the index that expose a live MCP server, ranked by agentic readiness. Use this when your agent needs to discover callable MCP endpoints for a domain ('payments', 'jobs', 'search') or overall. Pairs naturally with verify_mcp for a probe-before-use workflow.

Get the current status of the Execution Market MCP server and its integrations. Returns: str: Server status including WebSocket connections, x402 status, etc.

Auto-generate an A2A Agent Card from an MCP server's tool list. Each MCP tool is converted into an A2A skill. The resulting agent.json makes the MCP server discoverable by any A2A-compatible agent in Google's agent ecosystem. Defaults to ThinkNEO's own MCP server. Requires authentication.

Returns the full guide for the deBridge MCP server. CALL THIS FIRST.

List all versions of an MCP server - Returns all available versions for a specific MCP server, ordered by publication date (newest first)

A simple test tool to verify that the MCP server is working correctly

Add a remote MCP server or REST API to your workspace.

Look up the trust score for any MCP server by URL or npm package name. Returns score, grade, findings summary, and certification status.

Trigger a live trust scan of an HTTP or HTTPS MCP server. Returns trust score, grade, and security findings.

Get the current status of the Execution Market MCP server and its integrations. Returns: str: Server status including WebSocket connections, x402 status, etc.

Evaluate one or more headless CAS expressions server-side (MCP-only numeric mode). Unsupported expressions return a GUI handoff link.

Evaluate one or more headless CAS expressions server-side (MCP-only numeric mode). Unsupported expressions return a GUI handoff link.

Configure automatic top-up when balance drops below a threshold. The configuration lives ONLY in the current MCP session — it is held in memory by the MCP server process and is lost on server restart, MCP client reconnect, or server redeploy. Top-ups are signed locally with TRON_PRIVATE_KEY and sent to your Merx deposit address (memo-routed). For persistent auto-deposit you currently need to call this tool again at the start of each session.

Get specific MCP server version - Returns detailed information about a specific version of an MCP server. Use the special version `latest` to get the latest version.

Get ALTER MCP server installation instructions. Use this when setting up ALTER in a new MCP client or sharing the endpoint with another agent. Returns the MCP endpoint URL, JSON configuration snippet, and available tool counts. Free L0.

Get detailed information about a specific MCP server

[kiwi] Send feedback to the dev of the Kiwi MCP server.

Get current MCP server connection info: network name, node address, and latest block

Answers who can build an MCP server and explains how Walnai can design, implement, integrate, and deploy custom MCP servers for a business.

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.

Run a bounded JSON-RPC conformance probe against another MCP server. The input is a registry ``namespace/name`` string (e.g. ``"com.trycloudflare.candy-josh-writers-balance/yultrace-audit"``); the tool looks up the registry-published ``remotes[].url`` and runs the probe against that URL. Arbitrary URLs are NOT accepted — targets are whitelisted to the official MCP Registry's isLatest+active entries. The probe runs five bounded sub-tests (initialize, tools/list, malformed-body, unknown-method, oversized-params) under hard caps (10 HTTP requests; 30 s wall-clock; 500 KB per response; 50 KB final return size).

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")

Upload a dataset file and return a file reference for use with discovery_analyze. Call this before discovery_analyze. Pass the returned result directly to discovery_analyze as the file_ref argument. Provide exactly one of: file_url, file_path, or file_content. Args: file_url: A publicly accessible http/https URL. The server downloads it directly. Best option for remote datasets. file_path: Absolute path to a local file. Only works when running the MCP server locally (not the hosted version). Streams the file directly — no size limit. file_content: File contents, base64-encoded. For small files when a URL or path isn't available. Limited by the model's context window. file_name: Filename with extension (e.g. "data.csv"), for format detection. Only used with file_content. Default: "data.csv". api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.

Unlocks access to other MCP tools. All tools remain locked with a 'Session Not Initialized' error until this function is called. Returns essential rules for blockchain data interactions.

Fetch HTTP response headers for a URL. Use when inspecting server configuration, security headers, or caching policies.

Check if the API is responding. Returns status and server timestamp.

Run a bounded JSON-RPC conformance probe against another MCP server. The input is a registry ``namespace/name`` string (e.g. ``"com.trycloudflare.candy-josh-writers-balance/yultrace-audit"``); the tool looks up the registry-published ``remotes[].url`` and runs the probe against that URL. Arbitrary URLs are NOT accepted — targets are whitelisted to the official MCP Registry's isLatest+active entries. The probe runs five bounded sub-tests (initialize, tools/list, malformed-body, unknown-method, oversized-params) under hard caps (10 HTTP requests; 30 s wall-clock; 500 KB per response; 50 KB final return size).

Composite server-side investigation tool. Pass a question and the server automatically: (1) detects intent (aggregation/temporal/ordering/knowledge-update/recall), (2) queries the entity index for structured facts, (3) builds a timeline for temporal questions, (4) retrieves memory chunks with the right scoring profile, (5) expands context around sparse hits, (6) derives counts/sums for aggregation, (7) assesses answerability, and (8) returns a recommendation. Use this as your FIRST tool for any non-trivial question — it does the multi-step investigation that would otherwise take 4-6 individual tool calls. The response includes structured facts, timeline, retrieved chunks, derived results, answerability assessment, and a recommendation for how to answer.

WHEN: checking server status, loaded D365 version, or custom model path. Triggers: 'status', 'statut', 'is the server ready', 'how many chunks', 'index loaded'. Returns JSON with: status, indexed chunk count, loaded version, custom model path.

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

The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.

Submit a URL for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_status to check progress, then url_scanner_async_task_result to get the scan result. Async counterpart of url_scanner_scan for clients without native MCP Tasks support.

List all slide presentations created in the current MCP session. Returns URLs, themes, and timestamps for each presentation you've created.

Submit a URL for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_status to check progress, then url_scanner_async_task_result to get the scan result. Async counterpart of url_scanner_scan for clients without native MCP Tasks support.

Evaluate any MCP service for trustworthiness before spending money on it. Connects to the target server, checks reachability, governance declarations, tool definition quality, and audit endpoints. Returns a trust score from 0 to 100 with a recommendation: PROCEED, PROCEED WITH CAUTION, HIGH RISK, or DO NOT TRANSACT. No API key needed.

Bridge an MCP tool call to an A2A (Agent-to-Agent Protocol) agent. Translates the MCP tool_name and arguments into an A2A task, sends it to the target A2A agent, waits for completion, and translates the response back to MCP format. Use this to make any MCP tool accessible to A2A agents (Google's agent ecosystem). Requires authentication.

[STEP 1 OF 3 — CALL THIS FIRST, ALWAYS, BEFORE ANY OTHER TOOL] Verifies your MCP connection, org_id, and Bearer token are valid. If this fails, no other tool will work — stop and fix the connection. THE 3-STEP PROTOCOL every agent must follow in every session: 1. suma_ping() → confirm connection (you are here) 2. suma_wakeup() → inject zero-shot context for this developer 3. suma_search() → retrieve before you answer ANYTHING Do NOT skip to suma_search or suma_ingest without calling this first. A session with no suma_ping is a session flying blind. Returns: server version, org_id, tier, weight_profile, timestamp.

Submit feedback about the Senzing MCP server. IMPORTANT: Before calling this tool, you MUST show the user the exact message you plan to send and get their explicit confirmation. Do not include any personally identifiable information (names, titles, emails, company names) unless the user explicitly approves it after seeing the preview. Feedback is reviewed by the Senzing team. Feedback is not anonymous — submissions are logged and reviewed

Submit a URL with optional user intent for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_status to check progress, then url_scanner_async_task_result to get the scan result. Async counterpart of url_scanner_scan_with_intent for clients without native MCP Tasks support.

List all active MCP ↔ A2A bridge mappings and translation statistics. Shows which MCP servers are mapped to which A2A agents, plus 30-day translation stats (total, success rate, average latency). Requires authentication.

Get an upload URL to upload a single image to a project. Returns a pre-built upload URL and instructions. The caller must perform the actual upload using curl since the MCP server cannot access local files. This endpoint uploads images only. To add annotations, call annotations_save with the image ID from the upload response. For bulk uploads with annotations, use images_prepare_upload_zip.

Actively probe any URL to check if it is a live, spec-compliant MCP server. Sends a JSON-RPC tools/list request and verifies a valid response. Use this before depending on a third-party MCP endpoint — manifests and documentation can claim MCP support without actually serving it. Returns {verified: true/false, endpoint, note}.

Submit a URL for NHS to crawl and score. Use when you discover an agent-first tool, API, or service that isn't in the index yet. NHS will fetch the site, check its 7 agentic signals (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), compute a score, and add it to the index. The site becomes searchable within a few seconds if the crawl succeeds.

Compare 2-5 MCP servers side by side on the fields users actually decide on: security score, critical findings, pricing, transport mode, tool count, and install command availability. Use when a user is choosing between candidates from a search. Returns a structured comparison table plus a short per-field summary, so the agent can surface the important contrasts without a second pass over each server.

Download one completed encrypt result file through the gateway. This uses legacy was-util ``POST /result/url`` to obtain a signed URL, then fetches the file server-side so MCP clients do not depend on environment-specific external MinIO reachability. By default the response includes base64 when the file is small enough and always stores a local copy under ``data/downloads/<job_id>/`` unless ``save_to_path`` is provided.

REQUIRED onboarding entrypoint for A-Team MCP. MUST be called when user greets, says hi, asks what this is, asks for help, explores capabilities, or when MCP is first connected. Returns platform explanation, example solutions, and assistant behavior instructions. Do NOT improvise an introduction — call this tool instead.

Searches the official Quanti documentation (docs.quanti.io) to answer questions about using the platform. **When to use this tool:** - When the user asks "how to do X in Quanti?", "what is a connector?", "how to configure BigQuery?" - When the user needs help configuring or using a connector (Google Ads, Meta, Piano, etc.) - To explain Quanti concepts: projects, connectors, prebuilds, data warehouse, tag tracker, transformations - When the user asks about the Quanti MCP (setup, overview, semantic layer) **This tool does NOT replace:** - get_schema_context: to get the actual BigQuery schema for a client project - list_prebuilds: to list pre-configured reports for a connector - get_use_cases: to find reusable analyses - execute_query: to execute SQL **Available topic filters:** connectors, data-warehouses, data-management, tag-tracker, mcp-server, transformations