MCP servers for DeepSeek Harness

62,372 MCP servers on Mcprush that work with DeepSeek Harness.

62,372 MCP servers

Scanned where there is a package or repository to read, graded from its tool list where there is only an address — the grade is on each server's page
Works with DeepSeek Harness

Easily find and fix security issues in your applications leveraging Snyk platform capabilities.

144k/day
Free

MCP server for mobile app automation: verify, control, and debug iOS, Android, TV, and desktop apps

112k/day 1 tool
Free

Validate local data files, summarize profiles and detect PII without returning raw values.

33.9k/day
Free

Securely run LLM-generated code in isolated containers across 7 languages and 3 container backends.

31.7k/day 3 tools
Free

MCP servers on mcprush that work with DeepSeek Harness. DeepSeek Harness is a terminal harness, and working with it is a claim each publisher makes on their own listing — this shelf is every listing that makes it, and nothing else.

DeepSeek Harness can start a server on your own machine or reach a remote one over HTTP, so both halves of this shelf are open to it. Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. Narrowing further — by category, by price model, by how a server authenticates — keeps the client filter on, so nothing on the page stops being about DeepSeek Harness.

Nearly every server in this catalogue is connected straight to its publisher: the listing gives the publisher’s own address or start command, and mcprush is not in the path, so nothing is routed, metered or billed here. The exception is a server delivered through the mcprush gateway — there one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set, and installing it is a line of the mcprush CLI: npx mcprush@latest add, followed by the server’s id. The listing says which of the two it is before you install anything.

Compare
tick one more