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/sexylin/hipo-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/sexylin/hipo-mcp/hipo-work)<a href="https://agentmods.dev/mcp/sexylin/hipo-mcp/hipo-work"><img src="https://agentmods.dev/badge/mcp/sexylin/hipo-mcp/hipo-work/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/sexylin/hipo-mcp/hipo-work"><img src="https://agentmods.dev/badge/mcp/sexylin/hipo-mcp/hipo-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hipo-work 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
{
"hipo-work": {
"url": "https://mcp.hipowork.com/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.
- 11d ago First seen · 6 lines scan A ed0c193f6621
hipo-work is an MCP server published in the GitHub repository sexylin/hipo-mcp (0 stars, last pushed 2d 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
x-mcp-ai
Safety-first X (Twitter) API v2 MCP server: 41 typed tools across 12 packages, policy-gated. Runs locally from the x-mcp-ai npm package. Needs 18 environment variables to run.
Checkmarx
MCP server "Checkmarx" as configured in Checkmarx/cx-agentic-ai. Launched with sh ${PLUGIN_ROOT}/hooks/cx_run.sh mcp bridge.
checkmarx
Official Checkmarx MCP Server. Remote server at {cxone_base_url}.
travel-compliance
Travel-compliance intelligence and curated booking for digital nomads and long-stay travellers. Remote server at mcp.departi.eu.
cite-caddy
Remote MCP server for full read/write access to a Zotero library. Remote server at citecaddy.herbertkokholm.dk.
mcp_shield
MCP server "mcpshield" as configured in sanjibani/mcp-shield. Runs locally from the mcp_shield Python package.