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/meta-quest/webxr-first-steps/hzdbgit clone --depth 1 https://github.com/meta-quest/webxr-first-stepsWrote 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/meta-quest/webxr-first-steps/hzdb)<a href="https://agentmods.dev/mcp/meta-quest/webxr-first-steps/hzdb"><img src="https://agentmods.dev/badge/mcp/meta-quest/webxr-first-steps/hzdb.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hzdb 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 5d 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.
This is a copy
100% identical to hzdb — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"hzdb": {
"command": "npx",
"args": [
"-y",
"@meta-quest/hzdb",
"mcp",
"server"
]
}
}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.
- 5d ago First seen · 11 lines scan A d8f020711bec
hzdb is an MCP server published in the GitHub repository meta-quest/webxr-first-steps (177 stars, last pushed 3mo 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. It is 100% identical to hzdb, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
browser-game
Local tools for planning and validating focused browser-game prototypes. Runs locally from the opengame-browser-game-mcp npm package.
hzdb
Compatibility shim for @meta-quest/hzdb - now @meta-quest/metavr (Meta VR CLI). Installs and re-exports @meta-quest/metavr; install @meta-quest/metavr directly for the current name. Runs locally from the @meta-quest/hzdb npm package.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.
summer-engine
Local Summer CLI and MCP server for Summer Engine. Install and run the engine, connect Claude Code, Cursor, Codex, Gemini, and other agents, and build real games with bundled skills, hooks, and plugins. Runs locally from the summer-engine npm package.
rankedtoday-mcp
League of Legends MCP server — MMR estimation from LP flow, climb projections, KDA, hours played, and cognitive-readiness reference. No API key. Runs locally from the rankedtoday-mcp Python package.
blender-mcp-2-79
MCP server "blender-mcp-2-79" as configured in AaronBrunckhurst/blender-mcp-2.79. Runs locally from the blender-mcp-2-79 Python package.