Power Automate MCP Server by Flow Studio

GitHub Copilot agent skills for Power Automate via FlowStudio MCP — build, debug, and operate cloud flows programmatically

MCP Servers JavaScript Listed MIT

Is Power Automate MCP Server by Flow Studio safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 0%
Last push 67d ago
Compare Power Automate MCP Server by Flow Studio
Suggest a correction

In detail: Power Automate MCP Server by Flow Studio scores 38.1/100 (Grade D), ranked #1242 of 1374 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 3.0/10; recent commits are unsigned; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Power Automate MCP Server by Flow Studio could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Power Automate MCP Server by Flow Studio and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/ninihen1/power-automate-mcp-skills, MIT, last pushed 2026-09-04. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.0/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 4
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 10
  3. Published packages None

    No registry package. Power Automate MCP Server by Flow Studio is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 3.1/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Power Automate MCP Server by Flow Studio’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Power Automate MCP Server by Flow Studio compares in MCP Servers

  1. #715 Weapp Agent MCP 38.2 +0.1
  2. #716 Tijori Finance MCP 38.2 +0.1
  3. #717 Power Automate MCP Server by Flow Studio 38.1 this agent
  4. #718 MCP Power Automate 38.1 ±0
  5. #719 Just MCP Server 38.0 −0.1

Bars show each HVTrust score; the tick marks Power Automate MCP Server by Flow Studio’s 38.1.

Where the 38.1 comes from

HVTrust dimensions vs the MCP Servers average

38.1 / 100 · 100.0% confidence

Power Automate MCP Server by Flow Studio MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.8 / 25
7.0 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.5 / 20
4.7 below avg 12.2
AdoptionLog-scaled stars · package downloads
3.7 / 20
3.9 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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 67 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
29.8
Activity sub-score · out of 100
#717

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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 67 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
35
Forks
9
Last Push
2026-09-04
67 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
5
Rank Change
▼1
was #1241

Analysis

Activity Inputs

29.8 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
15.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.7 / 20

Common questions about Power Automate MCP Server by Flow Studio

Public trust evidence for Power Automate MCP Server by Flow Studio 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 Power Automate MCP Server by Flow Studio publish package provenance?
No published build provenance is currently detected for Power Automate MCP Server by Flow Studio. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Power Automate MCP Server by Flow Studio have an OpenSSF Scorecard?
Power Automate MCP Server by Flow Studio has an OpenSSF Scorecard score of 3.0/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 Power Automate MCP Server by Flow Studio actively maintained?
Slowing down. Last push was 67 days ago — keep an eye on whether activity resumes.
What license does Power Automate MCP Server by Flow Studio use?
Power Automate MCP Server by Flow Studio ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Power Automate MCP Server by Flow Studio's commits signed?
0% of the last 100 commits to Power Automate MCP Server by Flow Studio 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
Power Automate MCP Server by Flow Studio appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Power Automate MCP Server by Flow Studio'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-27
Activity Resumed
Activity resumed

Maintain Power Automate MCP Server by Flow Studio?

For maintainers

HVTrust scores Power Automate MCP Server by Flow Studio 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 22HVTrust 3Score 2Fresh 1Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1169 → #1180)
2026-10-04
Rank Moved
Rank dropped 40 spots (#1124 → #1164)
2026-10-04
Activity Score Changed
Activity score down 6pts (41 → 35)
2026-09-26
Rank Moved
Rank dropped 16 spots (#1080 → #1096)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 491 spots (#581 → #1072)
2026-09-23
HVTrust Changed
HVTrust up 9.6pts (34.9 → 44.5)
2026-09-22
Newly Listed
First tracked at rank #581
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank rose 39 spots (#1087 → #1048)
2026-09-12
Rank Moved
Rank dropped 14 spots (#1073 → #1087)
2026-09-11
Rank Moved
Rank dropped 10 spots (#1063 → #1073)
2026-09-09
Rank Moved
Rank dropped 14 spots (#1054 → #1068)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1044 → #1054)
2026-09-07
Rank Moved
Rank dropped 38 spots (#1006 → #1044)
2026-09-06
Rank Moved
Rank dropped 14 spots (#992 → #1006)
2026-09-05
Scorecard Added
OSSF Scorecard: 3.1/10
2026-09-05
Rank Moved
Rank rose 305 spots (#1297 → #992)
2026-09-05
HVTrust Changed
HVTrust up 24.7pts (19.5 → 44.2)
2026-09-03
Rank Moved
Rank dropped 22 spots (#1272 → #1294)
2026-09-02
Rank Moved
Rank dropped 21 spots (#1251 → #1272)
2026-09-01
Rank Moved
Rank dropped 16 spots (#1235 → #1251)
2026-08-31
Rank Moved
Rank dropped 22 spots (#1213 → #1235)
2026-08-30
Rank Moved
Rank dropped 20 spots (#1193 → #1213)
2026-08-29
Rank Moved
Rank dropped 23 spots (#1170 → #1193)
2026-08-28
Rank Moved
Rank dropped 24 spots (#1146 → #1170)
2026-08-27
Activity Resumed
Activity resumed
2026-08-27
Rank Moved
Rank rose 135 spots (#1281 → #1146)
2026-08-27
HVTrust Changed
HVTrust up 5.0pts (15.1 → 20.1)
2026-08-27
Activity Score Changed
Activity score up 24pts (24 → 47)
2026-08-26
Rank Moved
Rank dropped 18 spots (#1263 → #1281)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1233 → #1259)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 38.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/power-automate-mcp-server-by-flow-studio.svg)](https://hvtracker.net/agents/power-automate-mcp-server-by-flow-studio)
HTML:
<a href="https://hvtracker.net/agents/power-automate-mcp-server-by-flow-studio"><img src="https://hvtracker.net/badge/power-automate-mcp-server-by-flow-studio.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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