MCP servers observed by Lowdown
ai.trydock/dock MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 86 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.trydock/dock
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.trydock/dock?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 84 → 86
- 2026-11-13: input or output schemas changed, descriptions changed
What tools does it list?
86 tools on 2026-11-16:
add_columnadd_commentadd_videoaddress_bookappend_doc_sectionbulk_create_rowsbulk_update_rowscheck_workspace_privatecreate_file_uploadcreate_rowcreate_support_ticketcreate_surfacecreate_video_uploadcreate_webhookcreate_workspacedelete_filedelete_file_uploaddelete_rowdelete_surfacedelete_webhookdelete_workspacedowngrade_planedit_videoevaluate_formulaget_billingget_comment_threadget_docget_fileget_htmlget_recent_eventsget_rowget_video_transcriptget_workspaceget_workspace_schemainvite_to_orglist_api_keyslist_capabilitieslist_commentslist_connectable_appslist_fileslist_my_support_ticketslist_recent_fileslist_rowslist_sheet_functionslist_surfaceslist_videoslist_webhookslist_workspace_memberslist_workspacesmove_rowspull_capabilityreact_to_commentread_help_articleremove_videoremove_workspace_memberreply_to_commentrequest_connectionrequest_limit_increaserequest_revoke_agent_keyrequest_rotate_agent_keyresolve_commentrevoke_api_keyrevoke_file_sharerotate_api_keyrotate_webhook_secretsearchsearch_helpsend_messageshare_fileshare_workspaceunresolve_commentupdate_docupdate_doc_sectionupdate_htmlupdate_rowupdate_surfaceupdate_videoupdate_webhookupdate_workspaceupdate_workspace_memberupgrade_planupload_filevalidate_doc_markdownvalidate_formulavalidate_htmlwatch_video
MCP Registry declaration
- Registry name:
ai.trydock/dock - Declared version: 1.1.0
- Status: active
- Declared hosts:
trydock.ai
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:ai.trydock/dock", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.trydock/dock?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).