Is Awesome Copilot MCP Server safe to use?

Awesome Copilot MCP Server has an HVTrust score of 55.8/100 (Grade C), ranked #758 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Awesome Copilot MCP Server?

Awesome Copilot MCP Server scores 55.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 196 GitHub stars and is categorized under MCP Servers.

Awesome Copilot MCP Server

microsoft/mcp-dotnet-samples

A comprehensive set of samples of creating and using MCP servers and clients with .NET

MCP Servers C# Listed MIT

Is Awesome Copilot MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 4%

Last push 4d ago

Compare Awesome Copilot MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Awesome Copilot MCP Server scores 55.8/100 (Grade C), ranked #758 of 1325 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 6.2/10; 4% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Awesome Copilot MCP Server compares in MCP Servers

#418 Webull OpenAPI 56.1 +0.3
#419 Git MCP Server 56.1 +0.3
#420 Awesome Copilot MCP Server 55.8 this agent
#421 Pgedge Postgres MCP 55.7 −0.1
#422 Vibe Check MCP Server 55.7 −0.1

Bars show each HVTrust score; the tick marks Awesome Copilot MCP Server’s 55.8.

Where the 55.8 comes from

HVTrust dimensions vs the MCP Servers average

55.8 / 100 · 100.0% confidence

Awesome Copilot MCP Server MCP Servers average (775 agents)

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

8.0 / 25

2.3 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.6 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.3 / 20

4.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.5 / 20

1.7 below avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-25

Rank Moved

Rank dropped 19 spots (#732 → #751)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.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.

Compare with another agent Get email alerts for Awesome Copilot MCP Server View MCP Servers Report missing data

60.9

Activity sub-score · out of 100

#420

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 C 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-26

Activity & Reach

Stars

196

Forks

Last Push

2026-09-22

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #751

Analysis

Activity Inputs

60.9 / 100

StarsRepository reach

13.8 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

14.3 / 25

CommunityFork signal

8.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.2 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 8

Vulnerabilities 10

Common questions about Awesome Copilot MCP Server

Awesome Copilot MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Awesome Copilot MCP Server publish package provenance?

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

Does Awesome Copilot MCP Server have an OpenSSF Scorecard?

Awesome Copilot MCP Server has an OpenSSF Scorecard score of 6.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 Awesome Copilot MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 4 day(s).

What license does Awesome Copilot MCP Server use?

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

Are Awesome Copilot MCP Server's commits signed?

4% of the last 100 commits to Awesome Copilot MCP Server 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

medium confidence

Implemented

Awesome Copilot MCP Server 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

high confidence

Extensions

Extension based 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 Awesome Copilot MCP Server'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 → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Awesome Copilot MCP Server?

For maintainers

HVTrust scores Awesome Copilot MCP Server 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-25

Rank Moved

Rank dropped 19 spots (#732 → #751)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 35 spots (#692 → #727)

2026-09-23

HVTrust Changed

HVTrust up 25.4pts (31.0 → 56.4)

2026-09-22

Newly Listed

First tracked at rank #692

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade D → C

2026-09-19

Rank Moved

Rank rose 472 spots (#1191 → #719)

2026-09-19

HVTrust Changed

HVTrust up 18.3pts (38.2 → 56.5)

2026-09-18

Grade Changed

Trust grade C → D

2026-09-18

Rank Moved

Rank dropped 474 spots (#717 → #1191)

2026-09-18

HVTrust Changed

HVTrust down 18.3pts (56.5 → 38.2)

2026-09-17

Rank Moved

Rank rose 20 spots (#737 → #717)

2026-09-11

Rank Moved

Rank dropped 16 spots (#699 → #715)

2026-09-09

Rank Moved

Rank dropped 12 spots (#679 → #691)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 463 spots (#1133 → #670)

2026-09-07

HVTrust Changed

HVTrust up 18.7pts (38.4 → 57.1)

2026-09-06

Grade Changed

Trust grade C → D

2026-09-06

Rank Moved

Rank dropped 518 spots (#615 → #1133)

2026-09-06

HVTrust Changed

HVTrust down 18.7pts (57.1 → 38.4)

2026-09-05

Rank Moved

Rank dropped 76 spots (#539 → #615)

2026-09-04

Scorecard Added

OSSF Scorecard: 6.2/10

2026-09-04

Grade Changed

Trust grade D → C

2026-09-04

Rank Moved

Rank rose 731 spots (#1270 → #539)

2026-09-04

HVTrust Changed

HVTrust up 34.4pts (22.9 → 57.3)

2026-09-03

Rank Moved

Rank dropped 29 spots (#1241 → #1270)

2026-09-02

Rank Moved

Rank dropped 30 spots (#1211 → #1241)

2026-09-01

Rank Moved

Rank dropped 32 spots (#1179 → #1211)

2026-08-31

Rank Moved

Rank dropped 19 spots (#1160 → #1179)

2026-08-30

Rank Moved

Rank dropped 41 spots (#1119 → #1160)

2026-08-29

Rank Moved

Rank dropped 41 spots (#1078 → #1119)

2026-08-28

Rank Moved

Rank dropped 29 spots (#1049 → #1078)

2026-08-27

Rank Moved

Rank dropped 20 spots (#1029 → #1049)

2026-08-26

Rank Moved

Rank dropped 84 spots (#945 → #1029)

2026-08-19

Rank Moved

Rank dropped 12 spots (#950 → #962)

2026-08-17

Rank Moved

Rank rose 12 spots (#969 → #957)

2026-08-16

Rank Moved

Rank dropped 25 spots (#944 → #969)

2026-08-12

Rank Moved

Rank rose 11 spots (#945 → #934)

2026-08-10

Rank Moved

Rank dropped 54 spots (#887 → #941)

2026-08-08

Newly Listed

First tracked at rank #883

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/awesome-copilot-mcp-server.svg)](https://hvtracker.net/agents/awesome-copilot-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/awesome-copilot-mcp-server"><img src="https://hvtracker.net/badge/awesome-copilot-mcp-server.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.3 · Raw JSON