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.
npx agentmods add mcp/sidkandan/universal-remote-control/urc-coordinationgit clone --depth 1 https://github.com/sidkandan/universal-remote-controlWrote 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/sidkandan/universal-remote-control/urc-coordination)<a href="https://agentmods.dev/mcp/sidkandan/universal-remote-control/urc-coordination"><img src="https://agentmods.dev/badge/mcp/sidkandan/universal-remote-control/urc-coordination.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
urc-coordination 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 4d 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
{
"urc-coordination": {
"command": ".venv/bin/python3",
"args": [
"urc/core/server.py"
],
"env": {
"PYTHONPATH": "."
}
}
}What else .mcp.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.
- 4d ago First seen · 11 lines scan A 536362e19e33
urc-coordination is an MCP server published in the GitHub repository sidkandan/universal-remote-control (13 stars, last pushed 5mo 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
serena
MCP server "serena" as configured in codingSamss/all-my-ai-needs. Runs locally from the git+https://github.com/oraios/serena Python package.
codex
MCP server "codex" as configured in codingSamss/all-my-ai-needs. Runs locally from the git+https://github.com/codingSamss/codexmcp.git Python package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
magic
Magic MCP is now the 21st MCP. This package is a compatibility proxy kept for old configs - new setups should use npx @21st-dev/cli@latest init. Setup: https://21st.dev/mcp. Runs locally from the @21st-dev/magic npm package.