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/nkiyohara/corresync/corresync-corresyncgit clone --depth 1 https://github.com/nkiyohara/corresyncWrote 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/nkiyohara/corresync/corresync-corresync)<a href="https://agentmods.dev/mcp/nkiyohara/corresync/corresync-corresync"><img src="https://agentmods.dev/badge/mcp/nkiyohara/corresync/corresync-corresync.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
corresync 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 3d 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
{
"corresync": {
"args": [
"mcp",
"serve"
],
"command": "corr"
}
}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.
- 3d ago First seen · 9 lines scan A eff57c97d066
corresync is an MCP server published in the GitHub repository nkiyohara/corresync (1 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
gomodel
MCP server "gomodel" as configured in ENTERPILOT/GoModel. Runs in Docker (docker.io/enterpilot/gomodel:0.1.83). Needs 2 environment variables to run.
openflowkit-mcp
Local-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. Runs locally from the @vrun-design/openflowkit-mcp npm package.
graymatter
MCP server "graymatter" as configured in angelnicolasc/graymatter. Launched with graymatter mcp serve.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
flameox
Runtime evidence that helps agents trace, profile, and burn down hotspots in application and native code, GPU kernels, and inference stacks. Runs locally from the flameox 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.