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/jarmstrong158/agentsyncWrote 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/jarmstrong158/agentsync/agentsync)<a href="https://agentmods.dev/mcp/jarmstrong158/agentsync/agentsync"><img src="https://agentmods.dev/badge/mcp/jarmstrong158/agentsync/agentsync/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/jarmstrong158/agentsync/agentsync"><img src="https://agentmods.dev/badge/mcp/jarmstrong158/agentsync/agentsync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentsync 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 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 · 13 lines scan A 7b0d6dddbba8
agentsync is an MCP server published in the GitHub repository jarmstrong158/agentsync (0 stars, last pushed 2mo ago), 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
git-mcp-server
Comprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more. Runs locally from the @cyanheads/git-mcp-server npm package. Needs 2 environment variables to run.
git
MCP server "git" as configured in gabrimatic/mcp-web-search-tool. Runs in Docker (type=bind,src=/path/to/projects,dst=/path/to/projects).
bitbucket-mcp
MCP Server for Bitbucket API - Container optimized with configurable tools, structured output and slim responses. Runs locally from the bitbucket-mcp-py Python package.
shift-mcp-server
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously. Runs locally from the @cyanheads/shift-mcp-server npm package. Needs 1 environment variable to run.
mcp-server
Test management over MCP: author cases, run manual executions, cut releases, read health. Runs locally from the @m00nsolutions/mcp-server npm package. Needs 5 environment variables to run.
git-helper-ai-mcp
MCP server for git helper ai. Features parse diff, generate commit message, analyze branch. From MEOK AI Labs. Runs locally from the git-helper-ai-mcp Python package.