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/deepklarity/harness-kitWrote 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/deepklarity/harness-kit/mobile)<a href="https://agentmods.dev/mcp/deepklarity/harness-kit/mobile"><img src="https://agentmods.dev/badge/mcp/deepklarity/harness-kit/mobile/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/deepklarity/harness-kit/mobile"><img src="https://agentmods.dev/badge/mcp/deepklarity/harness-kit/mobile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mobile 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 1mo 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
{
"mobile": {
"command": "npx",
"args": [
"-y",
"@mobilenext/mobile-mcp@latest"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 9 lines scan A 3beb8d5a71ad
mobile is an MCP server published in the GitHub repository deepklarity/harness-kit (100 stars, last pushed 3mo ago), 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-30.
Other mcp servers, from other repositories
ollama
MCP server "ollama" as configured in fedec65/bettercallclaude. Runs ${CLAUDE_PLUGIN_ROOT}/mcp-servers/ollama/dist/index.js with node.
workflows-ch
MCP server "workflows-ch", hosted remotely at mcp.bettercallclaude.ch, as configured in fedec65/bettercallclaude.
swiss-caselaw
MCP server "swiss-caselaw", hosted remotely at mcp.opencaselaw.ch, as configured in fedec65/bettercallclaude.
droidagentkit
Local-first Android development MCP: Gradle, adb, logcat, lint, crash triage, Perfetto, visuals. Runs locally from the @droidagentkit/launcher npm package.
mcacp
MCP-to-ACP bridge — let any MCP client drive ACP coding agents. Runs locally from the mcacp npm package.
landlord-framework
MCP server "landlord-framework" as configured in DizzyMii/landlord. Runs locally from the landlord-framework Python package.