Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/tonytanglab/deepseek-harness-relay-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/tonytanglab/deepseek-harness-relay-mcp/harness-relay-mcp)<a href="https://agentmods.dev/mcp/tonytanglab/deepseek-harness-relay-mcp/harness-relay-mcp"><img src="https://agentmods.dev/badge/mcp/tonytanglab/deepseek-harness-relay-mcp/harness-relay-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/tonytanglab/deepseek-harness-relay-mcp/harness-relay-mcp"><img src="https://agentmods.dev/badge/mcp/tonytanglab/deepseek-harness-relay-mcp/harness-relay-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
harness-relay-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"harness-relay-mcp": {
"command": "node",
"args": [
"./dist/dsh-relay-proxy.mjs"
],
"cwd": "."
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 9 lines scan A fc82985716f5
harness-relay-mcp is an MCP server published in the GitHub repository tonytanglab/deepseek-harness-relay-mcp (3 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
deepseek-harness-plugin-mcp
MCP server "deepseek-harness-plugin-mcp" as configured in bobleer/deepseek-harness-plugin-mcp. Runs locally from the deepseek-harness-plugin-mcp npm package.
url-manager-mcp
URL Manager MCP Server — Agent-first web link collection & knowledge management. Runs locally from the url-manager-mcp Python package. Needs 2 environment variables to run.
dsh-mediacrawler
MCP server "dsh-mediacrawler" as configured in xwh-01/dsh-mediacrawler. Runs locally from the dsh-mediacrawler Python package.
guarftrain
Training Guardian — sidecar training monitor with crash recovery, agent decisions, MCP & web dashboard. Runs locally from the guarftrain Python package.
dsh-feed
A local index that combines GitHub data about the dsh-plugin topic with npm registry data. It can be queried by agent tools, a command-line program, or an MCP server.
dsh-artifact-promotion-proof
MCP server "dsh-artifact-promotion-proof" as configured in dongsheng123132/dsh-artifact-promotion-proof. Runs ${PLUGIN_ROOT}/mcp-server.mjs with node.