Skip to main content
Glama
315,293 tools. Last updated 2026-07-28 14:44

"Understanding and Using Docker Logs" matching MCP tools:

  • Simulate a call and return success, gas, decoded return, and best-effort state diff / asset changes / logs. Provide a high-level call (address + function + args) or raw (to + data), never both.
    Connector
  • Submit a Pair Profile take (registered pairs). source `agent_deep` = you, answering the deep binary form from your logs; `human_short` = your human's likert5 self-report. Answer only from actual log evidence — if you have none for a statement, answer `unobserved`; never guess or extrapolate. Scoring is deterministic — same answers, same type, no LLM. Raw responses accumulate: retake as your logs grow. Your observed profile of the human stays unpublished until they approve it.
    Connector
  • 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).
    Connector
  • Submit a song request to KAZM 106.5 FM & 780 AM via the station website. Searches the real studio library, then logs the request for the DJ — every request gets read. Provide both song title and artist for best results.
    Connector

Matching MCP Servers

  • F
    license
    -
    quality
    B
    maintenance
    MCP server for viewing Docker container logs on a remote VPS via SSH.
    Last updated
  • -
    license
    -
    quality
    -
    maintenance
    Enables reading Docker container logs and stats from remote servers via SSH, supporting container listing, log retrieval, stats, inspection, and Docker Compose logs.
    Last updated

Matching MCP Connectors

  • Security audit for docker-compose.yml — 25 checks: secrets, privileges, network, volumes, images.

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

  • Delete a story and all its media (files, versions, logs). This cannot be undone. Use list_stories to find story IDs.
    Connector
  • Submit a song request to KAZM 106.5 FM & 780 AM via the station website. Searches the real studio library, then logs the request for the DJ — every request gets read. Provide both song title and artist for best results.
    Connector
  • Calculate maximum TCP throughput using the Bandwidth-Delay Product (BDP) formula. Given link bandwidth and round-trip latency, computes the BDP (maximum in-flight data), achievable throughput with a given TCP window size, link utilization percentage, and recommended window size for full utilization. Critical for diagnosing slow transfers over high-latency links (WAN, VPN, satellite), tuning TCP buffers, and understanding why a 1Gbps link may only deliver 25Mbps with default 64KB windows. Applies to iperf testing, WAN optimization, and network capacity planning.
    Connector
  • Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.
    Connector
  • FREE endpoint. Submit an array of data or capability needs. The API returns details on matching endpoints we currently serve and automatically logs unmatched needs as roadmap requests.
    Connector
  • Agency mode only. Create a new app owned by the agent, start generation, and create a claim link for the client. Ownership transfers only when the invited client logs in with the same email and accepts the claim link.
    Connector
  • Record a firm's intent to claim its directory listing. Pre-OAuth, TESSA logs the claim and a representative reaches out via email within one business day to verify the claimant and switch the listing's verification status to 'claimed'. Full self-service OAuth-2.1 claim flow lands in a follow-up plan.
    Connector
  • Extracts certificate validity dates and expiration countdown for a domain using public certificate-transparency logs.
    Connector
  • Request a warm introduction to a Compliance Registry firm. target_firm_slug is required (this tool routes leads to listed firms, not to TESSA directly). TESSA logs the lead and forwards a warm intro email to the firm with TESSA Cc'd. No calendar booking.
    Connector
  • TLS certificate details (issuer, expiry, SANs) via Certificate Transparency logs.
    Connector