Is the Trydock Dock MCP server down?

mcp-registry/ai.trydock/dock · v1.0.0

healthy
Last checked 2026-10-27 03:28 UTC · handshake 158ms

As of 2026-10-27 03:28 UTC, the Trydock Dock MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
5,023
outages (90d)
3
tools
82

AI workspace for you, your team, and every agent. Tables, docs (images, 4K video), formulas.

Point your MCP client at this streamable-http endpoint: https://trydock.ai/api/mcp

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 4 warning(s) across 82 tool(s); ~25,147 tokens of tool definitions.
Scores higher than 1% of 15,773 MCP servers Glimind has audited.
Its tool list costs an agent ~25,147 tokens per session — more than 95% of servers.
66 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost35
Client compatibility70
Protocol100
Reliability100
Stability20

What to fix (6)

82 of 82 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_column, add_comment, add_video, address_book, append_doc_section and 77 more

82 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

31 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: address_book, bulk_create_rows, bulk_update_rows, create_file_upload, create_row and 26 more

Loading this server's tool list costs an agent ~25,147 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 23 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 65 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.trydock%2Fdock/fixes

add_column 1 change
{
  "name": "add_column",
  "description": "Append a single column to a workspace's table schema. Position is auto-computed as next-after-max so the contiguity invariant holds. Key collision (409) if a column with the same key already exists. Editor role required. Use this for per-column additions; use get_workspace_schema + update_surface with `columns` for full schema replacement or reordering. Multi-surface workspaces accept `surface_slug` to target a specific table sheet (use `list_surfaces` to enumerate); omit to fall through to the ",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug",
      "key",
      "label",
      "type"
    ],
    "properties": {
      "key": {
        "type": "string",
        "description": "Field name in row.data. Lowercase + underscores recommended; 1-64 chars."
      },
      "slug": {
        "type": "string",
        "description": "The workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL; both resolve to the same workspace."
      },
      "type": {
        "enum": [
          "text",
          "longtext",
          "number",
          "status",
          "person",
          "date",
          "url",
          "checkbox",
          "select"
        ],
        "type": "string",
        "description": "Column type. See get_workspace_schema for examples."
      },
      "label": {
        "type": "string",
        "description": "Human-readable header shown in the sheet."
      },
      "width": {
        "type": "number",
        "description": "Optional. Initial column width in px."
      },
      "options": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "color": {
              "type": "string"
            },
            "label": {
              "type": "string"
            },
            "value": {
              "type": "string"
            }
          }
        },
        "description": "Required for `status` + `select` types. The allowed values shown in the dropdown."
      },
      "description": {
        "type": "string",
        "description": "Optional. Human-readable tooltip shown in the column header. Up to 4000 characters (the same limit update_surface applies)."
      },
      "surface_slug": {
        "type": "string",
        "description": "Optional. The slug of the specific table surface to add the column to. Omit on single-table workspaces; required on multi-table workspaces if you don't want the primary table surface (lowest position)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
add_comment 1 change
{
  "name": "add_comment",
  "description": "Post a new comment on any target in a workspace: a row, a cell, a doc text range, an html element, an entire surface, or the workspace itself. Polymorphic target shape mirrors the REST POST /api/workspaces/:slug/comments. For threading, pass `parentId` to hang the new comment as a reply (the server flattens nested replies to single depth and auto-unresolves a resolved parent). Mentions are an array of `{ kind: 'user'|'agent', id, label }` triples; the server validates each mention's access to th",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug",
      "target",
      "body"
    ],
    "properties": {
      "body": {
        "type": "string",
        "description": "Comment body (plain text or markdown). 1-5000 chars."
      },
      "slug": {
        "type": "string",
        "description": "The workspace slug ('my-workspace' or 'my-org/my-workspace')."
      },
      "target": {
        "type": "object",
        "description": "Polymorphic target. Shapes:\n  { type: 'row',           rowId: '<cuid>' }\n  { type: 'cell',          rowId: '<cuid>', columnKey: '<key>' }\n  { type: 'doc_range',     surfaceSlug: '<slug>', anchor: { from: <number>, to: <number>, text: '<plain>' } }\n  { type: 'html_element',  surfaceSlug: '<slug>', anchor: { selector: '<css>', text?: '<plain>' } }\n  { type: 'video_frame',   surfaceSlug: '<slug>', anchor: { videoId: '<id from list_videos>', t: <seconds>, box?: { x, y, w, h } } }  (box in fractions of the frame, 0-1 from the top-left)\n  { type: 'surface',       surfaceSlug: '<slug>' }\n  { type: 'workspace' }",
        "additionalProperties": true
      },
      "mentions": {
        "type": "array",
        "items": {
          "type": "object",
          "additionalProperties": true
        },
        "description": "Optional `[{ kind, id, label }]` mentions. Each mention's principal must have workspace access. Fires inbox + email + webhook fan-out for newly-mentioned recipients only."
      },
      "parentId": {
        "type": "string",
        "description": "Optional parent comment id. When passed, this comment becomes a reply in the thread. Nested replies flatten to single-depth (reply-to-reply re-points at the root). Re-opens a resolved parent."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
add_video 1 change
{
  "name": "add_video",
  "description": "Add a video to the end of a video surface, from an https URL to an mp4, webm, mov or m4v file. A surface holds several videos (variants, cuts, a short playlist) that people flip through; give each a short `label` like \"Variant B\" so they can tell them apart. Create the surface first with `create_surface` and `kind: \"video\"`. Pass `content_type` when the URL has no file extension. For a file on your own machine, get a link with `create_video_upload` first. Dock downloads the file and keeps its OW",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug",
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "https URL of the video file. Dock stores its own copy."
      },
      "name": {
        "type": "string",
        "description": "Optional file or clip name. Max 200 chars."
      },
      "slug": {
        "type": "string",
        "description": "The workspace slug. Accepts bare or org-prefixed form."
      },
      "label": {
        "type": "string",
        "description": "Optional short label shown in the switcher, e.g. \"Variant B\". Max 60 chars."
      },
      "content_type": {
        "type": "string",
        "description": "Optional: video/mp4, video/webm, video/quicktime or video/x-m4v. Inferred from the URL's extension when omitted."
      },
      "surface_slug": {
        "type": "string",
        "description": "Optional video surface slug. Omit for the first video surface."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.trydock/dock"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.trydock/dock"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.trydock%2Fdock.svg)](https://glimind.com/server/mcp-registry%2Fai.trydock%2Fdock?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.trydock%2Fdock?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.trydock%2Fdock.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.trydock%2Fdock.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.trydock%2Fdock?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:68ab5d58b5a11862…, first seen 2026-10-27, included at leaf 76412 of 77,101. Version history · verify what your client received.

Tools (82)

Compare: most reliable database servers · most reliable communication servers · most reliable media servers · most reliable files servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Trydock Dock MCP server down right now?

As of 2026-10-27 03:28 UTC, the Trydock Dock MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Trydock Dock MCP server provide?

Trydock Dock MCP server advertises 82 tools, including add_column, add_comment, add_video, address_book, append_doc_section.

How do I install Trydock Dock MCP server?

Point your MCP client at this streamable-http endpoint: https://trydock.ai/api/mcp

Is the Trydock Dock MCP server safe to connect to an AI agent?

Glimind scanned all 82 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Trydock Dock MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve