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.
/plugin marketplace add advenimus/syncromsp-mcpnpx agentmods add plugins/advenimus/syncromsp-mcp/syncromspgit clone --depth 1 https://github.com/advenimus/syncromsp-mcpGrade A, and why
syncromsp 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 2d 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
{
"name": "syncromsp",
"description": "SyncroMSP PSA/RMM integration — bundles the MCP server (via npm) and the SyncroMSP skill (workflows, API quirks, ticket comment conventions, hyperlink rules).",
"author": {
"name": "Advenimus",
"url": "https://github.com/advenimus"
},
"homepage": "https://github.com/advenimus/syncromsp-mcp",
"repository": "https://github.com/advenimus/syncromsp-mcp",
"license": "MIT",
"userConfig": {
"subdomain": {
"type": "string",
"title": "Syncro subdomain",
"description": "The part before .syncromsp.com in your Syncro URL (e.g. 'mycompany' from mycompany.syncromsp.com). For legacy .shield.syncromsp.com accounts, still enter just the subdomain.",
"required": true
},
"api_key": {
"type": "string",
"title": "Syncro API key",
"description": "Generate at Admin → API Tokens in your Syncro account. Use the Custom Permissions tab to scope the token to the resources you need. The token is stored in your system keychain, not in plain text.",
"sensitive": true,
"required": true
}
}
}
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.
- 2d ago First seen · 27 lines scan A a5cf03e60f28
syncromsp is a plugin published in the GitHub repository advenimus/syncromsp-mcp (9 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
atlassian-mcp-server
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
scrumboy-board-operator
Agent plugin with Skills for operating Scrumboy boards through its MCP and Agoragentic APIs.
beans-prime
Configure Claude Code to track work using Beans.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills-only: owns folder layout and templates; runs the Obsidian CLI directly via the official obsidian-cli skill.
sw
The specwright ladder for Claude Code and Codex: init, propose, plan, implement, review, archive, ship, and delivery.
auto-enrich
Auto-enrich user prompts with context for Jira tickets, GitHub PRs/issues/repos/files, GitLab issues/MRs/projects/files, and Sentry issues.