Is KonQuest Meta Ads MCP safe to use?

KonQuest Meta Ads MCP has an HVTrust score of 34.9/100 (Grade D), ranked #1245 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for KonQuest Meta Ads MCP?

KonQuest Meta Ads MCP scores 34.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 44 GitHub stars and is categorized under MCP Servers.

KonQuest Meta Ads MCP

brandu-mos/konquest-meta-ads-mcp

57-tool supervised Meta Ads MCP server for Claude Code. Open-core: full CRUD, multi-asset ads, targeting, diagnostics, safety gates. Premium adds 41 tools: optimization engine, vault intelligence, copy generation.

MCP Servers Python Listed MIT

Is KonQuest Meta Ads MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.4 / 10

Provenance None

Signed commits 10%

Last push 156d ago

Compare KonQuest Meta Ads MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: KonQuest Meta Ads MCP scores 34.9/100 (Grade D), ranked #1245 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.4/10; 10% of recent commits are signed; last pushed 2026-04-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How KonQuest Meta Ads MCP compares in MCP Servers

#742 DevDocs 35.1 +0.2
#743 Kronan MCP 35.0 +0.1
#744 KonQuest Meta Ads MCP 34.9 this agent
#745 Fanout MCP 34.7 −0.2
#746 MCP Drawthings 34.7 −0.2

Bars show each HVTrust score; the tick marks KonQuest Meta Ads MCP’s 34.9.

Where the 34.9 comes from

HVTrust dimensions vs the MCP Servers average

34.9 / 100 · 100.0% confidence

KonQuest Meta Ads MCP MCP Servers average (775 agents)

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

2.2 / 25

8.1 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

9.7 / 17

2.5 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

1.6 / 20

10.5 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.6 / 20

1.6 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 56 spots (#1298 → #1242)

2026-09-23

HVTrust Changed

HVTrust up 22.0pts (13.1 → 35.1)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.4/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 156 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for KonQuest Meta Ads MCP View MCP Servers Report missing data

18.4

Activity sub-score · out of 100

#744

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 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-04-23

156 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #1245

Analysis

Activity Inputs

18.4 / 100

StarsRepository reach

9.9 / 30

FreshnessLast push recency

3.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.4 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

10%

of last 100 commits verified

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 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Common questions about KonQuest Meta Ads MCP

Public trust evidence for KonQuest Meta Ads MCP 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 KonQuest Meta Ads MCP publish package provenance?

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

Does KonQuest Meta Ads MCP have an OpenSSF Scorecard?

KonQuest Meta Ads MCP has an OpenSSF Scorecard score of 1.4/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 KonQuest Meta Ads MCP actively maintained?

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

What license does KonQuest Meta Ads MCP use?

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

Are KonQuest Meta Ads MCP's commits signed?

9% of the last 100 commits to KonQuest Meta Ads MCP 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

KonQuest Meta Ads MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency 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

How this surface has changed

Detected changes to KonQuest Meta Ads MCP'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain KonQuest Meta Ads MCP?

For maintainers

HVTrust scores KonQuest Meta Ads MCP 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 56 spots (#1298 → #1242)

2026-09-23

HVTrust Changed

HVTrust up 22.0pts (13.1 → 35.1)

2026-09-22

Newly Listed

First tracked at rank #1298

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 10 spots (#1210 → #1220)

2026-09-08

Rank Moved

Rank dropped 16 spots (#1194 → #1210)

2026-09-07

Rank Moved

Rank dropped 17 spots (#1177 → #1194)

2026-09-06

Rank Moved

Rank dropped 17 spots (#1160 → #1177)

2026-09-05

Rank Moved

Rank dropped 33 spots (#1127 → #1160)

2026-09-04

Rank Moved

Rank dropped 20 spots (#1107 → #1127)

2026-09-03

Scorecard Added

OSSF Scorecard: 1.4/10

2026-09-03

Rank Moved

Rank rose 116 spots (#1223 → #1107)

2026-09-03

HVTrust Changed

HVTrust up 12.2pts (23.9 → 36.1)

2026-09-02

Rank Moved

Rank dropped 36 spots (#1187 → #1223)

2026-09-01

Rank Moved

Rank dropped 38 spots (#1149 → #1187)

2026-08-31

Rank Moved

Rank dropped 34 spots (#1115 → #1149)

2026-08-30

Rank Moved

Rank dropped 43 spots (#1072 → #1115)

2026-08-29

Rank Moved

Rank dropped 44 spots (#1028 → #1072)

2026-08-28

Rank Moved

Rank dropped 37 spots (#991 → #1028)

2026-08-27

Rank Moved

Rank dropped 30 spots (#961 → #991)

2026-08-26

Rank Moved

Rank dropped 100 spots (#861 → #961)

2026-08-24

Rank Moved

Rank dropped 13 spots (#843 → #856)

2026-08-16

Rank Moved

Rank dropped 17 spots (#831 → #848)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-10

Rank Moved

Rank dropped 45 spots (#766 → #811)

2026-08-08

Newly Listed

First tracked at rank #769

GitHub → PyPI: konquest-meta-ads-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/konquest-meta-ads-mcp.svg)](https://hvtracker.net/agents/konquest-meta-ads-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/konquest-meta-ads-mcp"><img src="https://hvtracker.net/badge/konquest-meta-ads-mcp.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