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/phillipboesger/polarion-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/plugins/phillipboesger/polarion-mcp/plugin)<a href="https://agentmods.dev/plugins/phillipboesger/polarion-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/phillipboesger/polarion-mcp/plugin/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/plugins/phillipboesger/polarion-mcp/plugin"><img src="https://agentmods.dev/badge/plugins/phillipboesger/polarion-mcp/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
polarion-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 17d 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
{
"name": "polarion-mcp",
"version": "1.0.0",
"description": "Polarion ALM MCP tools and workflow guidance",
"mcpServers": {
"polarion": {
"command": "npx",
"args": ["-y", "polarion-mcp"],
"env": {
"API_BASE_URL": "${API_BASE_URL}",
"BEARER_TOKEN": "${BEARER_TOKEN}"
}
}
}
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 53 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 17d ago First seen · 16 lines scan A c5aaabacf045
polarion-mcp is a plugin published in the GitHub repository phillipboesger/polarion-mcp (6 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-25.
polarion-mcp compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| polarion-mcpphillipboesger/polarion-mcp | Plugin | 6 | 5d ago | MIT | A | — | Claude Code |
| rails-ai-contextcrisnahine/rails-ai-context | Plugin | 186 | 8d ago | MIT | A | — | Claude Code |
| boxlab marketplaceBoxLab-Ltd/yandex-metrica-mcp | Plugin | 15 | 6d ago | MIT | A | — | Claude Code |
| yandex-metrica-mcpBoxLab-Ltd/yandex-metrica-mcp | Plugin | 15 | 6d ago | MIT | A | — | Claude Code |
| papigetpapi/papi | Plugin | 11 | 6d ago | MIT | A | — | Claude Code |
| astravueAstravueOrg/astravue-mcp-server | Plugin | 12 | yesterday | Apache-2.0 | A | — | Gemini CLI |
| n8n-pro-mcp marketplacehelbertparanhos/n8n-pro-mcp | Plugin | 3 | 11d ago | MIT | A | — | Claude Code |