Dock MCP Server

https://trydock.ai/api/mcp Remote v1.0.0

Published by trydock.ai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

The AI workspace for you, your team, and every agent you run. Tables and docs, one live surface.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 5

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: create_surface → list_files → address_book. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow create_surface → list_files → address_book

medium Unconstrained URL/host parameter "url" on "create_webhook"MTC-CAP-007

Tool "create_webhook" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool create_webhook · inputSchema.properties.url

medium Tool "delete_file" can modify the filesystemMTC-CAP-002

Tool "delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool delete_file

low Mutating tool "delete_file" declares no destructiveHintMTC-CAP-005

Tool "delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool delete_file

low Unconstrained path parameter "file_id" on "delete_file"MTC-CAP-008

Tool "delete_file" takes a path parameter "file_id" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool delete_file · inputSchema.properties.file_id

Tools 70

Each tool and what it can reach — enumerated from the running server.

  • create_surfaceingests untrusted inputreads sensitive data
  • address_booknetwork egress
  • create_webhooknetwork egress
  • delete_filewrites files
  • delete_webhooknetwork egress
  • get_comment_threadingests untrusted input
  • get_fileingests untrusted input
  • get_rowingests untrusted input
  • get_workspaceingests untrusted input
  • list_filesreads sensitive data
Show 60 more tools ↓
  • rotate_webhook_secretnetwork egress
  • send_messagenetwork egress
  • share_fileingests untrusted input
  • update_docnetwork egress
  • update_surfaceingests untrusted input
  • update_webhooknetwork egress
  • add_columnno sensitive capability
  • add_commentno sensitive capability
  • append_doc_sectionno sensitive capability
  • bulk_create_rowsno sensitive capability
  • bulk_update_rowsno sensitive capability
  • create_rowno sensitive capability
  • create_support_ticketno sensitive capability
  • create_workspaceno sensitive capability
  • delete_rowno sensitive capability
  • delete_surfaceno sensitive capability
  • delete_workspaceno sensitive capability
  • downgrade_planno sensitive capability
  • evaluate_formulano sensitive capability
  • get_billingno sensitive capability
  • get_docno sensitive capability
  • get_htmlno sensitive capability
  • get_recent_eventsno sensitive capability
  • get_workspace_schemano sensitive capability
  • list_api_keysno sensitive capability
  • list_capabilitiesno sensitive capability
  • list_commentsno sensitive capability
  • list_my_support_ticketsno sensitive capability
  • list_recent_filesno sensitive capability
  • list_rowsno sensitive capability
  • list_sheet_functionsno sensitive capability
  • list_surfacesno sensitive capability
  • list_webhooksno sensitive capability
  • list_workspace_membersno sensitive capability
  • list_workspacesno sensitive capability
  • move_rowsno sensitive capability
  • pull_capabilityno sensitive capability
  • react_to_commentno sensitive capability
  • remove_workspace_memberno sensitive capability
  • reply_to_commentno sensitive capability
  • request_connectionno sensitive capability
  • request_limit_increaseno sensitive capability
  • request_revoke_agent_keyno sensitive capability
  • request_rotate_agent_keyno sensitive capability
  • resolve_commentno sensitive capability
  • revoke_api_keyno sensitive capability
  • revoke_file_shareno sensitive capability
  • rotate_api_keyno sensitive capability
  • searchno sensitive capability
  • share_workspaceno sensitive capability
  • unresolve_commentno sensitive capability
  • update_doc_sectionno sensitive capability
  • update_htmlno sensitive capability
  • update_rowno sensitive capability
  • update_workspaceno sensitive capability
  • update_workspace_memberno sensitive capability
  • upgrade_planno sensitive capability
  • validate_doc_markdownno sensitive capability
  • validate_formulano sensitive capability
  • validate_htmlno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 94/100 5 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/trydock-ai-api/badge.svg)](https://mcptrustchecker.com/registry/trydock-ai-api)
HTML
<a href="https://mcptrustchecker.com/registry/trydock-ai-api"><img src="https://mcptrustchecker.com/registry/trydock-ai-api/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/trydock-ai-api/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://trydock.ai/api/mcp --online

Use the free API → How scoring works

More in Learning & Documentation