"How to check console logs and network activity" 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

• portal_get_wallet_summaryA

  SQDA

  Summarize wallet activity and fund flow with shared overview, asset movement, counterparties, evidence pivots, and follow-up filters across supported networks. COMMON USER ASKS: - EVM wallet fund-flow triage - Solana wallet activity and fee flow FIRST CHOICE FOR: - one-call wallet analysis across supported VMs - suspicious wallet triage, fund-flow direction, counterparties, and next evidence pivots before drilling into raw records WHEN TO USE: - You want a single high-level answer about what one wallet has been doing and where value appears to move. - You want inbound/outbound flow, activity and asset-movement counterparties, largest movements within each asset, and exact next pivots before drilling into raw transactions or fills. - The user asks to investigate a suspicious wallet, stolen-funds path, exploit counterparty, or incident address. DON'T USE: - You need every raw record with full chain-specific fields and no summarization. EXAMPLES: - EVM wallet fund-flow triage: {"network":"base-mainnet","address":"0xabc...","timeframe":"24h"} - Solana wallet activity and fee flow: {"network":"solana-mainnet","address":"Vote111...","timeframe":"6h"}

  ConnectorNo auth

• portal_evm_query_logsA

  SQDA

  Query raw EVM logs with address/topic filters, common event aliases, earliest/latest scanning, and optional inline decoding. COMMON USER ASKS: - Recent USDC Transfer logs - First recent USDC Transfer log - Latest ERC721/pass mint ID and tx hash FIRST CHOICE FOR: - NFT or ERC721 mint lookups such as latest pass minted, token ID, and mint transaction hash - contract event questions where the user needs exact event evidence rather than wallet or transaction summaries WHEN TO USE: - You need event logs filtered by contract or topic signature. - You want decoded log hints while still keeping the raw log shape available. - You want the first or last matching event in a bounded block/time window. - You want common event names such as transfer, approval, swap, mint, or burn instead of remembering topic0 hashes. - You need the latest ERC721/pass mint in a bounded deployment/recent window: filter Transfer events with topic1 as the zero address, use scan_order=latest, limit=1, and decode=true to expose decoded_log.decoded.token_id plus transaction_hash. DON'T USE: - You only want token transfers, which are easier with the token-transfer tool. EXAMPLES: - Recent USDC Transfer logs: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"event":"transfer","limit":20} - First recent USDC Transfer log: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"event":"transfer","scan_order":"earliest","limit":1} - Latest ERC721/pass mint ID and tx hash: {"network":"base-mainnet","from_block":46020000,"to_block":46100000,"addresses":["0xE4E70FdF2Fc1147a7f35c4c5de88E6BeA63eeAfA"],"event":"transfer","topic1":["0x0000000000000000000000000000000000000000000000000000000000000000"],"scan_order":"latest","decode":true,"include_transaction":true,"limit":1} - Decode logs inline: {"network":"ethereum-mainnet","timeframe":"1h","topic0":["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"],"decode":true,"limit":10}

  ConnectorNo auth

• secret_scanA

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

  Scan text or code for leaked secrets: API keys (AWS, GCP, Azure, OpenAI, Anthropic, Stripe, GitHub, GitLab, Slack, Twilio, SendGrid, HuggingFace), private keys (RSA/EC/PGP), JWTs, database connection strings, Bearer tokens, and Basic auth headers. Returns a list of findings with type, severity, line number, and a redacted preview. Use before committing code, sharing logs, or sending text to an LLM. 100% regex-based, zero network calls.

  ConnectorNo auth

• deploy_logsA

  LayeroA

  Raw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neighbourhood of the fatal line. Come here when you need to look with your own eyes — the cause is vague, or you are interested in how the app behaves rather than in a failure. You get the TAIL. `truncated` says earlier lines were dropped; do not present the tail as the whole log. For build logs, package-manager network chatter is hidden BEFORE the tail is cut, so the tail holds meaningful lines; `noise_hidden` says how many were hidden and `include_noise=true` shows them.

  ConnectorOAuth

• deploy_logsA

  LayeroA

  Raw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neighbourhood of the fatal line. Come here when you need to look with your own eyes — the cause is vague, or you are interested in how the app behaves rather than in a failure. You get the TAIL. `truncated` says earlier lines were dropped; do not present the tail as the whole log. For build logs, package-manager network chatter is hidden BEFORE the tail is cut, so the tail holds meaningful lines; `noise_hidden` says how many were hidden and `include_noise=true` shows them.

  ConnectorAPI key

• 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

• portal_get_time_seriesA

  SQDA

  Build simple activity charts and other time-series views across supported VMs, including compare-previous windows and grouped EVM contract trends. COMMON USER ASKS: - Base transactions per 15m bucket - Compare two periods FIRST CHOICE FOR: - activity over time, compare-current-vs-previous, grouped trends, and simple activity charts WHEN TO USE: - You want chart-ready metric buckets over time. - You want a simple activity chart for a network, defaulting to a 6h interactive window unless a longer window is explicitly requested. - You want to compare the current period to the previous period. DON'T USE: - You need raw record lists instead of aggregated buckets. - You need DEX pool candles or OHLC output. EXAMPLES: - Base transactions per 15m bucket: {"network":"base-mainnet","metric":"transaction_count","duration":"6h","interval":"15m"} - Compare two periods: {"network":"solana-mainnet","metric":"transaction_count","duration":"1h","interval":"5m","compare_previous":true}

  ConnectorNo auth

• tfstatusA

  InsideOut (Riley)A

  MONITORING: Quick status check for Terraform deployments Check the current status of a Terraform deployment job. Use this tool to quickly check if a deployment is running, completed, or failed. Returns job status, job_id, and other metadata without streaming logs. Use tflogs to stream the actual deployment logs. REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs). **LIVENESS**: The response carries two distinct timestamps: - `updated_at` — last semantic change (only bumped when status / drift / version actually differ). Useful for sorting deployments; NOT a per-poll heartbeat. - `last_refresh_at` — last successful Oracle decode (stamped on every poll where reliable reached Oracle, even if nothing in the row changed). Use this to confirm reliable is still actively talking to Oracle for a long-running RUNNING job. Absent on rows that haven't been refreshed since the column was added. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.

  ConnectorNo auth

• tfstatusA

  InsideOut (Riley)A

  MONITORING: Quick status check for Terraform deployments Check the current status of a Terraform deployment job. Use this tool to quickly check if a deployment is running, completed, or failed. Returns job status, job_id, and other metadata without streaming logs. Use tflogs to stream the actual deployment logs. REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs). **LIVENESS**: The response carries two distinct timestamps: - `updated_at` — last semantic change (only bumped when status / drift / version actually differ). Useful for sorting deployments; NOT a per-poll heartbeat. - `last_refresh_at` — last successful Oracle decode (stamped on every poll where reliable reached Oracle, even if nothing in the row changed). Use this to confirm reliable is still actively talking to Oracle for a long-running RUNNING job. Absent on rows that haven't been refreshed since the column was added. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.

  ConnectorNo auth

• portal_tron_query_transactionsA

  SQDA

  Query raw Tron transactions: native TRX transfers, TRC-10 asset transfers, TriggerSmartContract calls by contract and method, or any contract type, with optional inline logs and internal transactions. COMMON USER ASKS: - Recent native TRX transfers - USDT transfer calls in a block window - TRX sent from one wallet FIRST CHOICE FOR: - native TRX transfers, TRC-10 transfers, and smart-contract calls on Tron - who sent TRX to an address on Tron, or which wallets called a Tron contract WHEN TO USE: - You need raw Tron transaction records with sender, recipient, amount in TRX, fee, energy, and success. - You want native TRX transfers to or from a wallet in a bounded window. - You want calls to a Tron contract such as USDT filtered by method (transfer, approve) or caller. - You want TRC-10 asset transfers by asset id. DON'T USE: - You need TRC-20 token events; those are logs, so use portal_tron_query_logs. - You need an Ethereum-compatible network; use portal_evm_query_transactions. EXAMPLES: - Recent native TRX transfers: {"network":"tron-mainnet","timeframe":"5m","kind":"transfer","limit":20} - USDT transfer calls in a block window: {"network":"tron-mainnet","from_block":84000000,"to_block":84000010,"contract_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"method":"transfer","limit":20} - TRX sent from one wallet: {"network":"tron-mainnet","timeframe":"1h","kind":"transfer","from_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"limit":20}

  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_network_statsA

  ~Alter IdentityA

  Get aggregate ~alter network figures. Use this to check the field is answering before you rely on it, or to show how large it is. Returns total identities, verified profiles, query volume and active agent count, as whole-network totals only; nothing here is attributable to any member, and no handle can be identified from it. Takes no parameters. Free L0, no authentication required.

  ConnectorNo auth

• adw.adw_535A

  AlpineDataWorks Intelligence ServerB

  Returns a 0-100 Ethereum network sentiment score (composite z-scores of active addresses and transaction count vs 30-day baselines, daily since 2015) with per-component attribution, ETH network-context tiles, and methodology_version. Call when the user asks about Ethereum on-chain activity, ETH network demand heating up or cooling off, or address/transaction trends, or when timing launches, deployments, or gas-sensitive operations. Directional indicator, not a trading signal. Updates: daily.

  ConnectorNo auth

• list_capabilitiesA

  Axcess — Design Accessibility EvaluationA

  Returns available evaluation tools, what they check, and their pricing. Call this first to understand what Axcess can evaluate and how much each evaluation costs. This tool is FREE. All evaluation tools require USDC payment on Base network. Returns: JSON with tool descriptions, pricing, and rubric categories.

  ConnectorNo auth

• search_api_docsA

  Soracom KnowledgeA

  Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.

  ConnectorNo auth

• get_network_infoA

  mcpA

  What the a16z speedrun talent network is, why a candidate would join, how joining works, and what happens after. Use this before pitching the network to a candidate so the description is accurate; joining itself is the join_network tool.

  ConnectorNo auth

• agora_catalogA

  Mnemos — memory as a serviceA

  FREE. Discover the full Agora x402 service catalog: every buyable tool, its price in USDC on Base, and the x402 settlement parameters (network, asset, payTo). Call this first to see what you can buy and how to pay.

  ConnectorNo auth

• vitna_preflightA

  VITNA — Agent Compliance PreflightA

  SAFETY / OVERSIGHT CHECK before a dangerous or destructive action (shell command, file deletion, DB statement, network call). Call this to have VITNA check the action BEFORE you run it: it flags dangerous shell / SQL / secret-exfil / prompt-injection / suspicious-network patterns and returns { decision: allowed|blocked|flagged }. RESPONSE SHAPE DEPENDS ON THE KEY: an unclaimed trial key gets the decision label only, because the pattern detail is what makes the classifier worth stealing. A claimed key additionally gets threat_category, severity, reason (the rule names that matched, never the matched text), a threats[] array and a redacted echo of what was scanned, plus a signed audit record the user can review. VITNA evaluates and records; it does NOT enforce, so treat blocked / flagged as a stop and get human approval. This is how a user keeps you in check. Heuristic pattern match, not a sandbox: novel or obfuscated payloads can pass.

  ConnectorNo auth

• portal_tron_query_logsA

  SQDA

  Query raw Tron (TVM) event logs by contract address and topics with common event aliases, the parent transaction hash on every row, and optional inline decoding. COMMON USER ASKS: - Recent USDT transfers on Tron - USDT transfers received by one wallet FIRST CHOICE FOR: - TRC-20 token transfer events on Tron such as USDT - contract event evidence on Tron with the parent transaction hash WHEN TO USE: - You need TRC-20 Transfer or Approval events for a token such as USDT on Tron. - You need event logs from a Tron contract filtered by topic signature or indexed address. - You want the exact transaction hash behind each Tron event. DON'T USE: - You want native TRX transfers or contract calls; use portal_tron_query_transactions. - You need an Ethereum-compatible network; use portal_evm_query_logs. EXAMPLES: - Recent USDT transfers on Tron: {"network":"tron-mainnet","timeframe":"5m","addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"event":"transfer","decode":true,"limit":20} - USDT transfers received by one wallet: {"network":"tron-mainnet","from_block":84000000,"to_block":84000100,"addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"event":"transfer","topic2":["TJLuVi6UhS3UTx5EUXNCoz9VNqP2gnPmyf"],"decode":true,"limit":20}

  ConnectorNo auth

• ios_safari_console_logsA

  Robot Actions — Remote Device ControlA

  Collect console logs, exceptions, and log entries from a Safari page on an iOS device over a time window. Enables the Runtime and Log domains, then listens for Runtime.consoleAPICalled, Runtime.exceptionThrown, and Log.entryAdded events, and returns an array of { level, text, url?, line?, source? }. This is a LIVE-WINDOW collector: it only captures events fired AFTER it attaches (plus the buffered history WebKit replays on enable), so triggering the logging from a SEPARATE tool call races the attach and is missed. To capture logs from an action, pass triggerJs (run inside the window). Default window: 5 000 ms. Maximum: 15 000 ms. Omit pageId to auto-pick the active page.

  ConnectorOAuth