MCP Server Polarion

MCP server for Polarion ALM — read and write documents, work items, test runs, traceability links, and comments from any

MCP Servers Python Grade A Listed MIT
80.2/100
Rank #93 of 1320
Compare MCP Server Polarion

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-02 · 2d ago
Recent change
Grade Changed +5

Is MCP Server Polarion safe? MCP Server Polarion scores 80.2/100 (Grade A), ranked #93 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.5/10; 100% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-02
Grade Changed
Trust grade B → A
2026-09-02
Rank Moved
Rank rose 10 spots (#101 → #91)
2026-09-01
Scorecard Added
OSSF Scorecard: 6.5/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
50.1
Activity sub-score · out of 100
#36

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 23:02 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
12
Forks
3
Last Push
2026-09-02
2 days ago
Commits (4 wk)
18
Downloads (7d)
157
pypi
HN mentions (30d)
Open Issues
2
Rank Change
▼2
was #91

Analysis

HVTrust Dimensions vs MCP Servers

80.2 / 100 · 100.0% confidence

MCP Server Polarion MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.6 / 25
11.0 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
2.2 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
17.0 / 20
4.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.6 / 20
0.7 below avg 6.3

Activity Inputs

50.1 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
2.8 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.5 / 10
OpenSSF Scorecard · scanned Sep 1, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 4
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 10
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is MCP Server Polarion safe?

Public supply-chain signals for MCP Server Polarion are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but MCP Server Polarion carries less obvious unverified-evidence risk than projects with thin signals.
Does MCP Server Polarion publish package provenance?
Yes. MCP Server Polarion's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MCP Server Polarion have an OpenSSF Scorecard?
MCP Server Polarion has an OpenSSF Scorecard score of 6.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Server Polarion actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does MCP Server Polarion use?
MCP Server Polarion ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Server Polarion's commits signed?
100% of the last 100 commits to MCP Server Polarion are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP Server Polarion appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain MCP Server Polarion?

For maintainers

HVTrust scores MCP Server Polarion from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 12Listed 1HVTrust 1Scorecard 1Grade 1
2026-09-02
Grade Changed
Trust grade B → A
2026-09-02
Rank Moved
Rank rose 10 spots (#101 → #91)
2026-09-01
Scorecard Added
OSSF Scorecard: 6.5/10
2026-09-01
Rank Moved
Rank rose 163 spots (#264 → #101)
2026-09-01
HVTrust Changed
HVTrust up 13.5pts (66.4 → 79.9)
2026-08-31
Rank Moved
Rank dropped 32 spots (#232 → #264)
2026-08-27
Rank Moved
Rank dropped 11 spots (#214 → #225)
2026-08-26
Rank Moved
Rank dropped 12 spots (#202 → #214)
2026-08-24
Rank Moved
Rank dropped 16 spots (#188 → #204)
2026-08-22
Rank Moved
Rank rose 24 spots (#212 → #188)
2026-08-20
Rank Moved
Rank dropped 16 spots (#187 → #203)
2026-08-19
Rank Moved
Rank dropped 11 spots (#176 → #187)
2026-08-13
Rank Moved
Rank dropped 13 spots (#150 → #163)
2026-08-12
Rank Moved
Rank rose 10 spots (#160 → #150)
2026-08-10
Rank Moved
Rank dropped 16 spots (#144 → #160)
2026-08-08
Newly Listed
First tracked at rank #143

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 80.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-server-polarion.svg)](https://hvtracker.net/agents/mcp-server-polarion)
HTML:
<a href="https://hvtracker.net/agents/mcp-server-polarion"><img src="https://hvtracker.net/badge/mcp-server-polarion.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON