MCP Risk

Directory / server

ai.trydock/dock

This directory entry reports an automated security scan of ai.trydock/dock, scanned 2026-07-28. Trust grade F rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via remote-tools-list

F 55/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as ai.trydock/dock. 1 finding
  • Registry entry: ai.trydock/dock ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 98 days ago
  • Stars: 0
  • License: MIT
  • Security policy (SECURITY.md): absent
INFO Published package is consistent and attested §1.3

No published package associated with this server (remote-only or non-npm/PyPI source).
PASS Tool surface is inspectable and proportionate §2.1–§2.4
66 tool(s) enumerated. Capabilities detected: network-egress, filesystem. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 11 findings
  • Tools exposed: 66
  • update_doc: network-egress
  • list_webhooks: network-egress
  • create_webhook: network-egress
  • update_webhook: network-egress
  • rotate_webhook_secret: network-egress
  • delete_webhook: network-egress
  • get_comment_thread: network-egress
  • list_files: filesystem
  • delete_file: filesystem
  • Detected capabilities: network-egress, filesystem
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://trydock.ai/api/mcp
FAIL Authentication required §3.2

Server answers anonymous requests (HTTP 200) while exposing non-trivial or unverifiable capabilities - fail per §3.2.
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://trydock.ai
INFO No known vulnerabilities (OSV.dev) §4.1

No package to query (remote-only server).
FAIL Server-supplied instructions free of poisoning indicators §5.1–§5.4
5 suspicious indicator(s) found in server-supplied instructions, tool descriptions, or schemas. 5 findings
  • server instructions: oversized: 7630 chars (limit 4096)
  • update_doc description: oversized: 4208 chars (limit 2048)
  • update_html description: oversized: 2411 chars (limit 2048)
  • update_doc: embedded URL: https://cdn.dock.ai/2025-launch-walkthrough.mp4
  • validate_html: non-http URI scheme: javascript:`/`data:text/html`
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.