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/Fino-wind/vaultbeat-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/fino-wind/vaultbeat-mcp/vaultbeat)<a href="https://agentmods.dev/mcp/fino-wind/vaultbeat-mcp/vaultbeat"><img src="https://agentmods.dev/badge/mcp/fino-wind/vaultbeat-mcp/vaultbeat/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/fino-wind/vaultbeat-mcp/vaultbeat"><img src="https://agentmods.dev/badge/mcp/fino-wind/vaultbeat-mcp/vaultbeat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vaultbeat 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 9d 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
{
"vaultbeat": {
"command": "uvx",
"args": [
"vaultbeat-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 9d ago First seen · 9 lines scan A 9c5c9349ce4b
vaultbeat is an MCP server published in the GitHub repository Fino-wind/vaultbeat-mcp (1 stars, last pushed 12d 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-30.
Other mcp servers, from other repositories
apple-health-ai-bridge
MCP server "apple-health-ai-bridge" as configured in roian6/apple-health-ai-bridge. Runs locally from the apple-health-ai-bridge Python package.
marrow
Self-hosted mirror and MCP server for Marrow, giving AI agents read-only access to your own Apple Health data. Runs locally from the marrow-mcp Python package. Needs 1 environment variable to run.
apple-health-semantic-mcp
MCP server "apple-health-semantic-mcp" as configured in Barbaroso/apple-health-semantic-mcp. Runs locally from the apple-health-semantic-mcp npm package.
blitz
Give AI agents full control over iOS/macOS development via a native macOS app with 30+ MCP tools. Runs locally from the @blitzdev/blitz-mcp npm package.
app-publish
MCP server for App Store Connect & Google Play Console — iOS/Android app management. Runs locally from the app-publish-mcp npm package. Needs 4 environment variables to run.
yapitalism
Evidence-backed reliability for voice-driven agent work. Runs locally from the yapitalism Python package.