Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/jarmstrong158, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
About
Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
Raise this grade
up to +16 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
Already earned (4) ▾Already earned (4) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.jarmstrong158/agentsync)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"agentsync": {
"command": "uvx",
"args": [
"agentsync-mcp"
]
}
}
}▶ Try itrun it locally
This is a local server, so it runs on your machine, not ours. Paste this to open it in the official MCP Inspector and poke at its tools:
npx @modelcontextprotocol/inspector uvx agentsync-mcp