ToolTrust
B15/100
DMontgomery40

deepseek-mcp-server

mcp0.5.0

@DMontgomery40

Model Context Protocol server for DeepSeek's advanced language models

By DMontgomery40 | 2 findings | Scanned 6/3/2026 | tooltrust-scanner/v0.3.13 | 339

1 High1 Info

Risk Summary

Safe With Normal Controls

Secret Handling is the main signal, but overall risk remains within an acceptable range.

Potential impact: Sensitive credentials may be read, logged, or leaked to external systems.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (2)

  • HighAS-010

    🔑Insecure Secret Handling

    deepseek_chat:input parameter "max_tokens" appears to accept a secret or credential

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • InfoAS-014

    ℹī¸Dependency Inventory Unavailable

    deepseek_chat:Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y deepseek-mcp-server"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade B](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-b.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)