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/iVamsi/droid-agent-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/ivamsi/droid-agent-kit/droidagentkit)<a href="https://agentmods.dev/mcp/ivamsi/droid-agent-kit/droidagentkit"><img src="https://agentmods.dev/badge/mcp/ivamsi/droid-agent-kit/droidagentkit/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/ivamsi/droid-agent-kit/droidagentkit"><img src="https://agentmods.dev/badge/mcp/ivamsi/droid-agent-kit/droidagentkit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
droidagentkit 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What else server.json configures
This page is one entry in a file that holds 2. 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 · 10 lines scan A 755aad88fc5e
droidagentkit is an MCP server published in the GitHub repository iVamsi/droid-agent-kit (1 stars, last pushed yesterday), with no licence file. 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
cli
PushToDisplay MCP server — send real-time updates to display boards on iOS and Android devices. Runs locally from the pushtodisplay npm package.
agent-droid-bridge
MCP server giving AI agents eyes and hands inside Android devices via ADB. Runs locally from the agent-droid-bridge Python package. Needs 16 environment variables to run.
server
Eyes and hands for AI agents on Android and iOS devices. Runs locally from the drengr npm package.
mobilerun
Control real Android and iOS devices with LLM agents — tap, swipe, type, automate flows. Remote server at api.mobilerun.ai.
sceneview
MCP server for SceneView — cross-platform 3D & AR SDK for Android and iOS. Gives your AI coding assistant the full SceneView SDK so it writes correct, compilable code. Runs locally from the sceneview-mcp npm package.
droidsight
Drives a real Android device over ADB and attaches the resulting screen to every action. Runs locally from the @edgecasehuman/droidsight npm package. Needs 9 environment variables to run.