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/sultanlive/vibeseo-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/sultanlive/vibeseo-mcp/vibeseo)<a href="https://agentmods.dev/mcp/sultanlive/vibeseo-mcp/vibeseo"><img src="https://agentmods.dev/badge/mcp/sultanlive/vibeseo-mcp/vibeseo/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/sultanlive/vibeseo-mcp/vibeseo"><img src="https://agentmods.dev/badge/mcp/sultanlive/vibeseo-mcp/vibeseo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibeseo 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.
What it actually says
{
"vibeseo": {
"url": "https://mcp.vibeseo.dev/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A b7dcac311264
vibeseo is an MCP server published in the GitHub repository sultanlive/vibeseo-mcp (2 stars, last pushed 22d 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
connectmachine
Manage your ConnectMachine contacts, networks, events, and digital business cards. Remote server at mcp.connectmachine.ai.
pulse-verity
MCP server for signed, verifiable Pulse Verity Index crypto prices and private API feedback. Runs locally from the pulse-verity npm package. Needs 1 environment variable to run.
alexandria
152-source digital library MCP server. Natural language search across academic papers, public domain books, legal records, government archives, and software documentation. Runs locally from the @the-40-thieves/alexandria-mcp npm package. Needs 1 environment variable to run.
hs-audit-app
MCP server "hs-audit-app", hosted remotely at hs-audit-app.oga-surf-project.workers.dev, as configured in ogasurfproject-jpg/horizon-shield.
hs-mcp-observatory
Public record of one read only walk over the official MCP registry: who answered, tools, who pays. Remote server at observatory.horizonshield.dev.
horizon-shield-webmcp
Agent intake desk for property renovation. Read only, CORS open, fail closed, receipts recompute. Remote server at web.horizonshield.dev.