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/HorizunGroup/horizun-pbi-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/horizungroup/horizun-pbi-mcp/horizun-pbi-mcp)<a href="https://agentmods.dev/mcp/horizungroup/horizun-pbi-mcp/horizun-pbi-mcp"><img src="https://agentmods.dev/badge/mcp/horizungroup/horizun-pbi-mcp/horizun-pbi-mcp/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/horizungroup/horizun-pbi-mcp/horizun-pbi-mcp"><img src="https://agentmods.dev/badge/mcp/horizungroup/horizun-pbi-mcp/horizun-pbi-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
horizun-pbi-mcp 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 12d 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
{
"horizun-pbi-mcp": {
"command": "uvx",
"args": [
"horizun-pbi-mcp"
],
"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.
- 12d ago First seen · 9 lines scan A 59d38e1ad2fd
horizun-pbi-mcp is an MCP server published in the GitHub repository HorizunGroup/horizun-pbi-mcp (13 stars, last pushed 7d ago), licensed Apache-2.0. 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
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
lightdash-docs
MCP server "lightdash-docs", hosted remotely at docs.lightdash.com, as configured in lightdash/lightdash.
sentry
Sentry's hosted MCP server: lets the agent search and read issues, errors and traces. Remote server at mcp.sentry.dev.
orionbelt-semantic-layer-mcp
Thin MCP server for OrionBelt Semantic Layer — delegates to REST API. Runs locally from the orionbelt-semantic-layer-mcp Python package.
teamcity
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants. Runs locally from the @daghis/teamcity-mcp npm package. Needs 3 environment variables to run.
vertex-o
MCP server "vertex-o", hosted remotely at {company}.vertexinc.com, as configured in vivy-yi/finance-skills.