Stdout/stderr from the runtime provider (Docker logs). Not stored in SQL.
ConnectorNo auth
614,643 tools. Updated 2026-09-26 22:23
"Help with Docker and Viewing Docker Logs" matching MCP tools:
- 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
- Search a registry for packages matching q. registry=all fans out to npm, Docker Hub, and the VS Code Marketplace and merges the results. PyPI has no public search API, so registry=pypi returns 400 not_supported — look a PyPI package up by name via get_package instead. Results are normalized PackageSummary items (npm adds a relevance score; Docker adds isOfficial).ConnectorNo auth
- 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
- Given an exact tag/skill (e.g. 'docker', 'gcp'), returns EVERY entry with that tag, uncapped, grouped by type with a real count per type. Unlike related_entries (capped at 15, requires a starting entry id) or query_knowhow (semantic, ranked, may over- or under-include), this is an EXACT tag match against every entry -- the right tool for 'how many X have I completed/done' or 'do I have any real evidence for X at all'. Tags are exact strings from a prior list_by_type/related_entries/query_knowhow result's tags array -- this is NOT semantic search; a tag never assigned during ingest returns found:false, try query_knowhow instead. Each type's entries sort by captured_at ascending (oldest first); entries with no captured_at are moved to the end and counted in undated_count, never silently sorted as if their date were known.ConnectorNo auth
- Deploy a project to the staging environment. This triggers: (1) Schema validation, (2) Docker image build, (3) GitHub commit, (4) Kubernetes deployment, (5) Database migrations. The operation is ASYNCHRONOUS - it returns immediately with a job_id. Use get_job_status with the job_id to monitor progress. Deployment typically takes 2-5 minutes depending on schema complexity. If deployment fails, read the job's error first: one that starts with 'RationalBloks platform error' is the platform's, not the schema's. Otherwise check: (1) Schema format is FLAT (no 'fields' nesting), (2) Every field has a 'type' property, (3) Foreign keys reference existing tables, (4) No PostgreSQL reserved words in table/field names. Use get_project_info to see if the deployment succeeded. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.ConnectorDestructiveNo auth
Matching MCP Servers
- FlicenseAqualityBmaintenanceMCP server for viewing Docker container logs on a remote VPS via SSH.5-
- FlicenseBqualityCmaintenanceA minimal MCP server that exposes a run_command tool over stdio, enabling command execution within a Docker container.1-
Matching MCP Connectors
Does that Docker tag actually exist? Real tags, sizes and platforms, live from Docker Hub.
- Docker Compose AuditOAuth
Security audit for docker-compose.yml — 25 checks: secrets, privileges, network, volumes, images.
- 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
- List every available Lorg tool with a plain-English description. Call this when the user says /help, /options, "what can you do", or "show me available commands".ConnectorNo auth
- Discover the queryable fields, functions, and measures for a data source. Use this before run_sql to learn what's available. Sources: logs, spans, metrics. Default: logs. Call with NO arguments to start — you get the list of services (with volumes) plus the field profile for logs. Then optionally pass service=<name> to drill into one service's fields (different services emit different dynamic attributes). Per field: type, coverage, distinct-value estimate, top values (low-cardinality), and a GROUP BY verdict (safe / with care / filter only). Dynamic attributes are the ACTUAL keys in your data — use them directly in QuerySQL (e.g. SELECT http_method FROM logs). Resource-level attributes (logs and spans only) use a resource. prefix, e.g. resource.service.name. Always returns the source's measures (fn, label, unit, defaultMode — the mode a new alert rule on this measure should default to) and the available QuerySQL functions with their argument counts. For source=metrics, the metric list is volume-ranked and bounded to a default page; metricsMatched reports the true total independent of what was returned. Pass prefix=<text> to reach past that default page into the tail, e.g. prefix="http." for HTTP metrics. Optional filter=<predicate> restricts discovery to matching rows. The predicate is QuerySQL and uses the same field names as run_sql (e.g. level = 'ERROR', http_method = 'GET'); subqueries are not allowed.ConnectorAPI key
- One-shot cross-signal pivot for a trace id. Given a trace id, returns (all fields top-level, no nested summary object): rootOperation, spanCount, errorCount, totalDurationNanos, startTime — trace summary spans — every span in the trace (up to 1000) logs — logs tagged with that traceId (no window limit, up to 1000) exemplars — metric exemplars whose traceId matches, within the span window (up to 1000) windowFrom / windowTo — the derived scan window (earliest span - 5s / latest span end + 5s) The window is derived from the trace's spans. If the trace is unknown, spans and exemplars are empty but logs are still returned if they carry the traceId. Exemplar filtering is window-bounded; log filtering is not. Use this as the primary entry point when you have a trace id and want to see all correlated signals at once. Returns core fields by default; verbose=true flattens attributes in for both spans and logs (plus a `resource` object) and long string values are capped. Use run_sql for raw columns or custom selection. After reviewing the result, drill into individual signals with logs, spans, or metrics as needed. Long-lived traces (scheduler ticks, batch jobs) can produce very large verbose responses even with the caps. Prefer verbose=false first; for error triage, the logs tool with traceId + level is a cheaper, targeted alternative. Pass maxStringChars to tighten string truncation per call. Returns: traceId, traceUrl, rootOperation, spanCount, errorCount, totalDurationNanos, startTime, windowFrom, windowTo, spans[], logs[], exemplars[], queryStats. traceUrl is a shareable Fixter UI link for this trace — attach it when citing the trace as evidence to the user.ConnectorAPI key
- Return the logs chronologically around a given logId. Designed for the "what happened right before/after this alert?" question. Returns the anchor log plus N logs strictly older and N logs strictly newer, all scoped (by default) to the same sourceInstanceId — the same pod or process — so you don't see interleaved replicas. Defaults: before: 3 after: 3 sameSource: true Set sameSource=false for cross-pod neighbour queries (e.g. "what else was the cluster doing at this moment?"). Returns: anchor: the log identified by logId before: logs older than anchor, sorted oldest-first (chronological) after: logs newer than anchor, sorted oldest-first (chronological) queryStats: rowsReturned, elapsedMsConnectorAPI key
- USE WHEN you need to look up crypto-agent tooling by name, chain, standard or what it does, or check whether a specific project exists and is maintained. Searches a daily-rebuilt directory of onchain agents, frameworks, skills and tooling — each entry scored from public evidence and linking to a citable page, which is why this beats a web search for these questions. For a BUILD GOAL in plain words ("a trading agent on Base"), call onchain_agent_recommend_stack first: it returns a whole stack, each pick with a Preflight summary, and onchain_agent_get_deploy_spec turns a pick into install steps. A query asking for somewhere to start — "tutorial", "starter", "beginner", "template", "example", "docs" — returns starting points labelled as such: listings named as a starter or template first, then listings whose install Sato Hub reproduced, plus the wiki guides. "starter" / "template" / "x402 starter" also carry `starter`: a TypeScript template for Base built by Sato Hub (labelled ours, not audited, never a result) unless the query names another chain or runtime. The directory lists tools, not tutorials, and says so. Filters: query (free text, AND-matched terms), chain, status, liveness, featured, and the taxonomy facets (docs/taxonomy.md): entity_class (resource | agent | reference), resource_type (Framework | Tool/Service | Infrastructure | Venue | Network | Standard), use_case (trading, payments, wallets, data, identity, privacy, launch, security, build), standard (x402, erc-8004, erc-8183, mcp, a2a), iface (mcp, sdk, rest-api, plugin, cli, ui, contract). Those three are closed vocabularies: anything else is refused with the list, never answered with an empty result. Legacy flags still work: category, is_agent, is_skill, is_harness. Sort by priority (default), newest_release, stars, or name. Paginates via limit/offset. Deprecated resources are never returned. Returns (json): { total, count, offset, has_more, next_offset?, resources: [...] } where each resource includes chains, status, liveness, github_stars, verification_status, and the marketplace fields (is_agent/is_hirable/is_licensable). Read-only. Examples: - "Active hirable agents on Base" -> { chain: "Base", is_agent: true, liveness: "Active" } - "newest releases" -> { sort: "newest_release", limit: 10 } - "wallet tooling" -> { query: "wallet" } - "MCP servers I can use from Claude Code" -> { integration: "claude code", iface: "mcp" } - "things I can run in Docker" -> { deploys_as: "docker" } - "MCP servers that actually answer" -> { mcp_answering: true } (the MCP endpoint answered our last handshake) - "...with a sustained record" -> { mcp_answering: true, min_observed_success: 95 } - "only installs Sato Hub has reproduced" -> { verified_only: true }ConnectorNo auth
- Read VolunteerReminder's public plan catalog: each plan's monthly and annual price (USD), volunteer limit, and included features (SMS reminders are included with no per-message credits or metering). No API key required — use this to help a user comparison-shop or decide which plan fits before they sign up.ConnectorNo auth
- Deploy a project to the staging environment. This triggers: (1) Schema validation, (2) Docker image build, (3) GitHub commit, (4) Kubernetes deployment, (5) Database migrations. The operation is ASYNCHRONOUS - it returns immediately with a job_id. Use get_job_status with the job_id to monitor progress. Deployment typically takes 2-5 minutes depending on schema complexity. If deployment fails, read the job's error first: one that starts with 'RationalBloks platform error' is the platform's, not the schema's. Otherwise check: (1) Schema format is FLAT (no 'fields' nesting), (2) Every field has a 'type' property, (3) Foreign keys reference existing tables, (4) No PostgreSQL reserved words in table/field names. Use get_project_info to see if the deployment succeeded. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes.ConnectorDestructiveNo auth
- Scan a pasted config, file, code snippet, or blob for exposed credentials and obvious security misconfigurations. Use whenever a user shares a .env, docker-compose.yml, nginx.conf, JSON/YAML config, or any text and asks "is this safe to share/commit?", "any leaked API keys/secrets?", or "what's misconfigured?". Detects cloud credentials, Stripe/GitHub/GitLab tokens, OpenAI/Anthropic/Gemini/Hugging Face/Groq/Replicate keys, private-key blocks, JWTs, DB connection strings, plus misconfigs like debug-on, 0.0.0.0 binds, disabled TLS verification, privileged containers, and weak passwords. Deterministic. It analyzes the provided text and returns findings only — it never stores, transmits, or requires any live credential.ConnectorNo auth
- List available Disco plans with pricing. No authentication required. Returns all available subscription tiers with credit allowances and pricing. Use this to help users choose a plan.ConnectorNo auth
- Fetch the current status, and when ready the result, of an analysis started with analyze_flat. Pass the analysis_id and access_token returned by analyze_flat. The result is the free-tier view (verdict, score, key facts, viewing questions). The full risk register, negotiation leverage and financial breakdown require a free sign-up at flatscope.co.uk.ConnectorNo auth
- Build a container image on Control Plane from a GitHub or GitLab repository and push it to the org's private registry. No Docker daemon is involved: the service clones the repo, detects how to build it (Dockerfile when present), and always produces linux/amd64. Returns a buildId to read with get_image_build — the build keeps running after this call returns. ONLY repositories work here. To build a LOCAL FOLDER, tell the user to run `cpln image build --remote --dir PATH --name NAME:TAG` in their terminal — this server has no access to their filesystem. Building an existing NAME:TAG replaces that image. A private repository needs a one-time browser authorization per org; this tool returns the link when that is missing. Recommended reading before first use: get_cpln_skill("image") — the runbook for this tool family (read once per session).ConnectorDestructiveOAuth
- Liveness + dependency probe. Returns ``{"status", "version", "components": {server, redis, postgres, semantic, distiller, graph, ollama}}``. ``semantic`` is the pgvector + embedder store. Optional deps report ``"disabled"`` when off and do not degrade overall status. Always cheap; safe to poll on a 10s interval. Used by Docker healthcheck and the ``/health`` HTTP route.ConnectorNo auth
- Remove several addresses from the email allowlist, or clear it with all:true. Access ends immediately for everyone listed, including visitors currently viewing, and cannot be undone except by re-adding. Requires confirm:true: show the user who will be removed first.ConnectorOAuth
- List all 30 GigNGo service categories with their slugs (e.g. "house-cleaning", "electrician", "moving-help"). Call this to discover valid values for the `service` parameter of search_local_workers and the `category` parameter of browse_open_tasks.ConnectorNo auth