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/loosedays/vibsync-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/loosedays/vibsync-mcp/vibsync)<a href="https://agentmods.dev/mcp/loosedays/vibsync-mcp/vibsync"><img src="https://agentmods.dev/badge/mcp/loosedays/vibsync-mcp/vibsync/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/loosedays/vibsync-mcp/vibsync"><img src="https://agentmods.dev/badge/mcp/loosedays/vibsync-mcp/vibsync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibsync 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 2mo 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
{
"vibsync": {
"type": "http",
"url": "https://mcp.vibsync.com/mcp"
}
}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.
- 2mo ago First seen · 6 lines scan A b6d6a1a18074
vibsync is an MCP server published in the GitHub repository loosedays/vibsync-mcp (0 stars, last pushed 20d ago), licensed MIT. 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
enquire-mcp
Long-term memory for AI agents — your Obsidian vault as searchable persistent memory. Runs locally from the @oomkapwn/enquire-mcp npm package.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
agentmemory
MCP server "agentmemory" as configured in Obidel/Agentmemory. Runs locally from the agentmemory npm package. Needs 3 environment variables to run.
agentmemory-cloud
MCP server "agentmemory-cloud", hosted remotely at agentmemory-dusky.vercel.app, as configured in Obidel/Agentmemory.
supermemory
MCP server "supermemory" as configured in YashvantHange/SuperMemory. Launched with supermemory-agent --storage .supermemory --transport stdio. Needs 1 environment variable to run.
agent-checkpoint-mcp
Local MCP server that saves work-in-progress checkpoints so any AI agent can resume a multi-step plan exactly where a previous session was cut off. Runs locally from the agent-checkpoint-mcp Python package.