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/ExpertVagabond/ibmz-mcp-serverWrote 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/expertvagabond/ibmz-mcp-server/ibmz)<a href="https://agentmods.dev/mcp/expertvagabond/ibmz-mcp-server/ibmz"><img src="https://agentmods.dev/badge/mcp/expertvagabond/ibmz-mcp-server/ibmz/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/expertvagabond/ibmz-mcp-server/ibmz"><img src="https://agentmods.dev/badge/mcp/expertvagabond/ibmz-mcp-server/ibmz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ibmz 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 11d 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
{ "ibmz": { "command": "npx", "args": [ "-y", "ibmz-mcp-server" ], "env": {} } }
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.
- 11d ago First seen · 10 lines scan A 0ead6ac85882
ibmz is an MCP server published in the GitHub repository ExpertVagabond/ibmz-mcp-server (0 stars, last pushed 4d 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
pdf-suite-mcp
37 tools to read, create, merge, split, watermark, fill, redact & search PDFs. Local, no API key. Runs locally from the pdf-suite-mcp npm package.
pdf-toolkit-mcp
Legacy PDF Toolkit identity, pinned to its 2.1.1 package; maintained successor: PDF Suite MCP. Runs locally from the pdf-suite-mcp npm package.
shopify-mcp
MCP server for Shopify Admin API — product, order, customer, inventory, and fulfillment management. Runs locally from the @purplesquirrel/shopify-mcp npm package.
guardrails
AI Agent Guardrails MCP server - security layer. Runs locally from the guardrails-mcp-server npm package.
universal-blockchain
ZetaChain universal blockchain MCP server. Runs locally from the universal-blockchain-mcp npm package.
ibmcloud
IBM Cloud CLI MCP server. Runs locally from the ibmcloud-mcp-server npm package.