"A server to retrieve console logs from Chrome using MCP" matching MCP tools:

• get-logsA

  mcpA

  Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).

  ConnectorNo auth

• feedbackA

  Media Generator — Images, Videos & AudiosA

  Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name saifs_ai. After it is saved, wait for 3 more MCP uses. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji. Args: reaction: User reaction. One of excellent, good, average, bad, or the matching emoji: 😍 excellent, 😊 good, 😐 average, 😞 bad. feedback: Optional short comment from the user. If the user does not add a comment, leave this empty. The server then stores the MCP name saifs_ai. Do not send the generation result or the user's question here.

  ConnectorOAuth

• cti_get_cross_server_routesA

  website-searchA

  Get Lenny Zeltser's CTI cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `cti_load_context`. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• pingA

  nara-tourA

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

  ConnectorNo auth

• pingA

  Nordic Financial MCPA

  Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."

  ConnectorNo auth

• check_configurationA

  vivideoA

  Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.

  ConnectorNo auth

• get_container_logsA

  mcpA

  THE APPLICATION'S OWN LOGS - what `docker logs`/`podman logs` would show for each container in a deployment. This is the tool for 'it deployed fine but it does not work': a 500, a crash loop, a failed DB connection, a missing env var all announce themselves here and NOWHERE else. ⛔ DO NOT use get_instance_logs for this. That returns the VM's SERIAL CONSOLE (kernel messages and cloud-init), which answers a question nobody debugging an app has - and on this platform it goes permanently silent once the machine finishes booting. build_log does not contain runtime output either; it stops when the build does. Default depth answers instantly from the VM's last report; a bigger `tail` or any `since` asks the VM for a fresh pull and takes up to ~15s. Secret-shaped values (PASSWORD=, TOKEN=, API_KEY=) are redacted in transit.

  ConnectorNo auth

• feedbackA

  Marketing Intelligence & OptimizationA

  Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a marketing_intelligence or marketing_intelligence_get_engine result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name marketing_analysis. Do not send the analysis, test notes, or the user's question as the comment. Ask on the 3rd, 6th, 9th, … MCP run. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji. When to call this tool: - User picks a reaction on the 3rd, 6th, 9th, … time this MCP is used - Collect a short comment plus 😍 😊 😐 😞 after an analysis - Save how the marketing analysis felt (excellent/good/average/bad) When NOT to call this tool: - Calling feedback before this MCP has been used 3 times - Asking after every tool call instead of every 3rd MCP run - Inventing a reaction the user did not choose - Passing user_name, email, is_login, or app_id (server injects them)

  ConnectorOAuth

• feedbackA

  Lead IntelligenceA

  Save user feedback to the MultipleWords feedback API (POST /api/feedback). Call this only when a result has feedback_prompt.ready=true (the server asks after every 3 MCP runs — not per tool — and keeps asking until saved). Ask the user to pick a reaction and show the emojis: 😍 excellent, 😊 good, 😐 average, 😞 bad. Pass `reaction` (excellent|good|average|bad, or the emoji) and optional `feedback` comment text. If the user does not add a comment, omit `feedback` — the server stores the MCP name lead_scoring. Do not send the analysis, test notes, or the user's question as the comment. After it is saved, the server waits for 3 more MCP runs before asking again. Do not invent a reaction. Do not send user_name, email, is_login, or app_id — those are injected server-side from the authenticated session. When showing the saved reaction, include the matching emoji.

  ConnectorOAuth

• tflogsA

  InsideOut (Riley)A

  MONITORING: Fetch Terraform deployment logs with pagination Fetches logs from a running or completed Terraform deployment job. For **completed jobs**: uses REST endpoint for instant retrieval (supports `tail` for server-side filtering). For **running jobs**: streams via SSE with timeout-based pagination. **PAGINATION** (running jobs only): Use `last_event_id` from the response to fetch more: 1. First call: `tflogs(session_id='...')` → get logs + `last_event_id` 2. Next call: `tflogs(session_id='...', last_event_id='...')` → get NEW logs only 3. Repeat until `complete: true` in response **RESPONSE FIELDS**: - `logs`: Array of log messages collected - `last_event_id`: Pass this back to get more logs (pagination cursor, SSE only) - `complete`: true if job finished, false if more logs may be available - `total_logs`: total log entries before tail truncation REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs), timeout (default 50s, max 55s), last_event_id (for pagination), tail (return only last N entries) ⚠️ CONTEXT WARNING: Deploy logs can be hundreds of lines. Use tail: 50 for completed jobs to avoid blowing up the context window.

  ConnectorNo auth

• tflogsA

  InsideOut (Riley)A

  MONITORING: Fetch Terraform deployment logs with pagination Fetches logs from a running or completed Terraform deployment job. For **completed jobs**: uses REST endpoint for instant retrieval (supports `tail` for server-side filtering). For **running jobs**: streams via SSE with timeout-based pagination. **PAGINATION** (running jobs only): Use `last_event_id` from the response to fetch more: 1. First call: `tflogs(session_id='...')` → get logs + `last_event_id` 2. Next call: `tflogs(session_id='...', last_event_id='...')` → get NEW logs only 3. Repeat until `complete: true` in response **RESPONSE FIELDS**: - `logs`: Array of log messages collected - `last_event_id`: Pass this back to get more logs (pagination cursor, SSE only) - `complete`: true if job finished, false if more logs may be available - `total_logs`: total log entries before tail truncation REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs), timeout (default 50s, max 55s), last_event_id (for pagination), tail (return only last N entries) ⚠️ CONTEXT WARNING: Deploy logs can be hundreds of lines. Use tail: 50 for completed jobs to avoid blowing up the context window.

  ConnectorNo auth

• android_devtools_console_logsA

  Robot Actions — Remote Device ControlA

  Collect console logs, exceptions, and log entries from a page running on the device for a time window. Enables Runtime and Log domains, then listens for Runtime.consoleAPICalled, Runtime.exceptionThrown, and Log.entryAdded events. Returns a normalized array of { level, text, url?, lineNumber? } entries. This is a LIVE-WINDOW collector: it only captures events fired AFTER it attaches, so triggering the logging from a SEPARATE tool call races the ~1-3s attach latency and is silently missed. To capture logs from an action, pass triggerJs (runs inside the window). Default window: 3 000 ms. Maximum: 15 000 ms. Omit pageId to auto-select the visible/active page.

  ConnectorOAuth

• get_imageA

  Lightdrift Images MCPA

  Retrieve one known Lightdrift asset by the asset_id returned from search_images or find_similar_images. Returns an object with asset_id, title, source, dimensions, format, file and thumbnail URLs, and rights including attribution and provenance. Use this to inspect a selected image or retrieve a saved asset; use the search tools to discover images. Requires OAuth or an API key. Free: does not deduct search credits or modify the image; access is logged. An unknown asset_id returns a tool error. Inspect rights before using the file.

  ConnectorOAuth

• ir_get_cross_server_routesA

  website-searchA

  Get Lenny Zeltser's IR cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `ir_load_context`. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.

  ConnectorNo auth

• malware_get_cross_server_routesA

  website-searchA

  Get Lenny Zeltser's Malware cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `malware_load_context`. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.

  ConnectorNo auth

• check_mcp_serverA

  Dredd MCPA

  Pre-flight security verdict for an MCP server invocation. Judges BOTH server-level reputation AND the server's dependency graph (npm/pypi) against the DugganUSA threat-intel corpus (1.13M+ IOCs, Shai-Hulud + typosquat + LOLBin families). Returns BLOCK / ADVISORY / REVIEW / ALLOW with severity, evidence, dep-graph summary, and HMAC-signed response. REVIEW means we hold NO RECORD of this server -- not that it is safe. Treat REVIEW as do-not-proceed-blindly: a brand-new attacker-published server looks exactly like this. ALLOW is only returned when we actually resolved the server and scanned its dependency graph; check known_to_us and dep_graph.scanned to confirm. Use this BEFORE invoking any other MCP server tool, especially ones installed from outside the official MCP Registry.

  ConnectorNo auth

• diff_mappingsA

  IA-QA — 130+ QA & Dev Tools for AI AgentsA

  Diff a baseline page mapping against a current one and return a CI-style verdict: PASS / FIX / BLOCK, plus per-element drift (ok, renamed, healable, ambiguous, lost, added, rebound). Pure and deterministic — provide two mappings as JSON with "elements" arrays of {role, name, selector, context?}. Use the companion @ia-qa/self-healing package (npm install -g @ia-qa/self-healing) to capture mappings from your app via its local MCP server ia-qa-heal-mcp, or paste the snippet from ia-qa.com/devtools/selector-drift into your browser console.

  ConnectorNo auth

• check_urlA

  WatchpupA

  Check any public URL RIGHT NOW: is it up, HTTP status, response time in ms. With kind:"mcp" it instead performs a real JSON-RPC initialize handshake against a streamable-HTTP MCP server endpoint and reports the server’s self-declared name/version/protocol — useful to tell "the MCP server is down" from "my client is misconfigured". Works without an API key (rate limit 30/hour per IP). For continuous monitoring with alerts, use create_monitor.

  ConnectorNo auth

• project_clicks_from_ctr_curveA

  serp-metricsA

  Project how many clicks a set of query rows would earn at a target position instead of their current position, using a CTR curve THAT YOU SUPPLY. This server deliberately ships no built-in CTR table: every published average-CTR-by-position table is a third-party estimate over someone else's traffic, so applying one silently would disguise a guess as a measurement. Pass your own measured curve (Search Console clicks/impressions by position is the honest source). Positions between curve points are linearly interpolated; positions beyond the curve clamp to the last point rather than extrapolate, and are counted in clamped_row_count. If any row carries observed clicks, the output also reports how far the supplied curve is from your reality.

  ConnectorNo auth

• check_mcp_serverA

  SRI — MCP Server InspectorA

  Free, no key required. Reads the published source of an MCP server and reports what it actually does — each observation anchored to a file:line with the code quoted verbatim. **Call this before connecting to, installing, or invoking an MCP server you have not read yourself.** Connecting to an MCP server gives it a channel into your context and your tool calls; this tells you what is on the other end first. Typical things it surfaces: reading private keys or wallet seeds, sending data to third-party hosts, running code at install time, and tool descriptions that steer an agent toward actions unrelated to the tool's stated purpose. Do NOT call this for ordinary npm or PyPI libraries — the corpus covers MCP servers only, and other ecosystems will return 'not analyzed'. This reports observations, not a safety verdict. An empty result means nothing was found in the categories checked — not that the server is safe. Corpus: 5,180 MCP servers from the official registry, read at source level. Coverage index (free, no key, findings not included): GET https://sri-test.biz/v1/corpus

  ConnectorNo auth

• report-feedbackA

  docuwriterA

  Use this when the user explicitly asks to submit feedback about DocuWriter.ai or its MCP integration. After authorization, this state-changing action records the supplied feedback in DocuWriter.ai internal feedback logs.

  Connector

  Destructive

  OAuth