Is MCP Power Automate safe to use?

MCP Power Automate has an HVTrust score of 28.7/100 (Grade D), ranked #1229 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Power Automate?

MCP Power Automate scores 28.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 24 GitHub stars and is categorized under MCP Servers.

MCP Power Automate

kaael1/mcp-power-automate

Local Power Automate MCP server, browser extension, and installable Codex skill.

MCP Servers TypeScript Grade D Listed MIT

28.7/100

Rank #1229 of 1320

Compare MCP Power Automate

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-06-01 · 95d ago

Recent change

Rank +12

Is MCP Power Automate safe? MCP Power Automate scores 28.7/100 (Grade D), ranked #1229 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.2/10; 21% of recent commits are signed; last pushed 2026-06-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#721 Bhived MCP — 28.9 (D) → #722 Crawleo MCP — 28.8 (D) → #724 Tijori Finance MCP — 28.7 (D) → #725 Apple Docs MCP — 28.5 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 257 spots (#972 → #1229)

2026-09-04

HVTrust Changed

HVTrust down 13.8pts (42.5 → 28.7)

2026-09-03

Rank Moved

Rank dropped 60 spots (#912 → #972)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.2/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 95 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MCP Power Automate View MCP Servers Report missing data

25.4

Activity sub-score · out of 100

#723

In MCP Servers

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

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-06-01

95 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼257

was #972

Analysis

HVTrust Dimensions vs MCP Servers

28.7 / 100 · 67.0% confidence

MCP Power Automate MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

3.8 / 25

5.7 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

10.4 / 17

1.4 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

5.7 / 20

6.5 below avg 12.2

AdoptionLog-scaled stars · package downloads

3.4 / 20

2.8 below avg 6.2

Activity Inputs

25.4 / 100

StarsRepository reach

8.4 / 30

FreshnessLast push recency

11.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.2 / 10

OpenSSF Scorecard · scanned Aug 29, 2026

Signed Commits

21%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 1

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Is MCP Power Automate safe?

Public trust evidence for MCP Power Automate is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does MCP Power Automate publish package provenance?

No published build provenance is currently detected for MCP Power Automate. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Power Automate have an OpenSSF Scorecard?

MCP Power Automate has an OpenSSF Scorecard score of 2.2/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 Power Automate actively maintained?

Slowing down. Last push was 95 days ago — keep an eye on whether activity resumes.

What license does MCP Power Automate use?

MCP Power Automate ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Power Automate's commits signed?

21% of the last 100 commits to MCP Power Automate 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 Power Automate appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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

How this surface has changed

Detected changes to MCP Power Automate's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-30

Activity Went Stale

No commits for 90 days

Maintain MCP Power Automate?

For maintainers

HVTrust scores MCP Power Automate 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-04

Rank Moved

Rank dropped 257 spots (#972 → #1229)

2026-09-04

HVTrust Changed

HVTrust down 13.8pts (42.5 → 28.7)

2026-09-03

Rank Moved

Rank dropped 60 spots (#912 → #972)

2026-09-02

Rank Moved

Rank rose 228 spots (#1140 → #912)

2026-09-02

HVTrust Changed

HVTrust up 13.7pts (28.9 → 42.6)

2026-09-01

Rank Moved

Rank dropped 42 spots (#1098 → #1140)

2026-08-31

Rank Moved

Rank dropped 28 spots (#1070 → #1098)

2026-08-30

Activity Went Stale

No commits for 90 days

2026-08-30

Rank Moved

Rank dropped 54 spots (#1016 → #1070)

2026-08-29

Scorecard Added

OSSF Scorecard: 2.2/10

2026-08-29

Rank Moved

Rank rose 218 spots (#1234 → #1016)

2026-08-29

HVTrust Changed

HVTrust up 11.0pts (17.9 → 28.9)

2026-08-28

Rank Moved

Rank dropped 15 spots (#1219 → #1234)

2026-08-26

Rank Moved

Rank dropped 36 spots (#1175 → #1211)

2026-08-24

Rank Moved

Rank dropped 10 spots (#1165 → #1175)

2026-08-16

Rank Moved

Rank dropped 28 spots (#1144 → #1172)

2026-08-10

Rank Moved

Rank dropped 66 spots (#1076 → #1142)

2026-08-08

Newly Listed

First tracked at rank #1071

GitHub → npm: @kaael1/mcp-power-automate

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-power-automate.svg)](https://hvtracker.net/agents/mcp-power-automate)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-power-automate"><img src="https://hvtracker.net/badge/mcp-power-automate.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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