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/WYRE-AI/syncro-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/wyre-ai/syncro-mcp/syncro-mcp)<a href="https://agentmods.dev/mcp/wyre-ai/syncro-mcp/syncro-mcp"><img src="https://agentmods.dev/badge/mcp/wyre-ai/syncro-mcp/syncro-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/wyre-ai/syncro-mcp/syncro-mcp"><img src="https://agentmods.dev/badge/mcp/wyre-ai/syncro-mcp/syncro-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
syncro-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 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
{
"syncro-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/syncro-mcp:v1.4.9"
],
"env": {
"SYNCRO_SUBDOMAIN": "",
"SYNCRO_API_KEY": "",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}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 · 18 lines scan A 4a07ddd684c1
syncro-mcp is an MCP server published in the GitHub repository WYRE-AI/syncro-mcp (4 stars, last pushed yesterday), licensed Apache-2.0. 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
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in WYRE-AI/connectwise-manage-mcp. Runs in Docker (ghcr.io/wyre-ai/connectwise-manage-mcp:v1.9.0). Needs 8 environment variables to run.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.2). Needs 6 environment variables to run.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.7.15). Needs 7 environment variables to run.
superops-mcp
MCP server "superops-mcp" as configured in WYRE-AI/superops-mcp. Runs in Docker (ghcr.io/wyre-ai/superops-mcp:v2.0.1). Needs 6 environment variables to run.
salesbuildr-mcp
MCP server "salesbuildr-mcp" as configured in WYRE-AI/salesbuildr-mcp. Runs in Docker (ghcr.io/wyre-ai/salesbuildr-mcp:v1.5.8). Needs 5 environment variables to run.
planka
MCP server for PLANKA kanban boards. Full CRUD for cards, tasks, comments, and labels. Runs locally from the @gogogadgetbytes/planka-mcp npm package. Needs 3 environment variables to run.