updated 2026-11-11 00:08 UTC

Markifact: AI Performance Marketing

Repository Website

MCP server for Google Ads, Meta Ads, GA4, TikTok Ads, and LinkedIn Ads. Manage 300+ ad operations from Claude, ChatGPT, Gemini, Cursor, or any AI client. Human-in-the-loop on every write.

MCP Servers Shell Listed MIT

Is Markifact: AI Performance Marketing safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 0%
Last push yesterday
Compare Markifact: AI Performance Marketing

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Markifact: AI Performance Marketing scores 49.2/100 (Grade D), ranked #1029 of 1387 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 4.5/10; recent commits are unsigned; last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Markifact: AI Performance Marketing 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Markifact: AI Performance Marketing 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/markifact/markifact-mcp, MIT, last pushed 2026-11-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Mixed

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

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

  3. Published packages None

    No registry package. Markifact: AI Performance Marketing 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.8/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 Markifact: AI Performance Marketing’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.

Signed credential (JSON) How to verify

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 Markifact: AI Performance Marketing compares in MCP Servers

  1. #582 NotebookLM MCP (PleasePrompto) 49.5 +0.3
  2. #583 Mac Control MCP 49.3 +0.1
  3. #584 Markifact: AI Performance Marketing 49.2 this agent
  4. #585 Synter Media AI MCP Server 49.2 ±0
  5. #586 MCP Server 12306 49.0 −0.2

Bars show each HVTrust score; the tick marks Markifact: AI Performance Marketing’s 49.2.

Where the 49.2 comes from

HVTrust dimensions vs the MCP Servers average

49.2 / 100 · 100.0% confidence

Markifact: AI Performance Marketing MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.6 / 25
5.2 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
12.3 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
15.0 / 20
2.7 above avg 12.3
AdoptionLog-scaled stars · package downloads
4.3 / 20
3.3 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Rank Moved
Rank rose 64 spots (#1093 → #1029)
2026-11-10
Activity Score Changed
Activity score up 7pts (42 → 50)
2026-11-08
Rank Moved
Rank rose 12 spots (#1102 → #1090)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/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
View MCP Servers Report missing data
49.8
Activity sub-score · out of 100
#584
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 →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
59
Forks
8
Last Push
2026-11-10
yesterday
Commits (4 wk)
5
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #1029

Analysis

Activity Inputs

49.8 / 100
StarsRepository reach
10.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
4.4 / 20

Common questions about Markifact: AI Performance Marketing

Public trust evidence for Markifact: AI Performance Marketing 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 Markifact: AI Performance Marketing publish package provenance?
No published build provenance is currently detected for Markifact: AI Performance Marketing. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Markifact: AI Performance Marketing have an OpenSSF Scorecard?
Markifact: AI Performance Marketing has an OpenSSF Scorecard score of 4.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 Markifact: AI Performance Marketing actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Markifact: AI Performance Marketing use?
Markifact: AI Performance Marketing ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Markifact: AI Performance Marketing's commits signed?
0% of the last 100 commits to Markifact: AI Performance Marketing 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
Markifact: AI Performance Marketing 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 Markifact: AI Performance Marketing'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

Maintain Markifact: AI Performance Marketing?

For maintainers

HVTrust scores Markifact: AI Performance Marketing 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
Rank 35Score 4HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-11-10
Rank Moved
Rank rose 64 spots (#1093 → #1029)
2026-11-10
Activity Score Changed
Activity score up 7pts (42 → 50)
2026-11-08
Rank Moved
Rank rose 12 spots (#1102 → #1090)
2026-11-03
Rank Moved
Rank dropped 12 spots (#1083 → #1095)
2026-10-31
Rank Moved
Rank dropped 17 spots (#1064 → #1081)
2026-10-30
Rank Moved
Rank rose 44 spots (#1108 → #1064)
2026-10-30
Activity Score Changed
Activity score up 6pts (40 → 46)
2026-10-28
Rank Moved
Rank dropped 14 spots (#1091 → #1105)
2026-10-26
Rank Moved
Rank dropped 16 spots (#1076 → #1092)
2026-10-20
Rank Moved
Rank dropped 14 spots (#1055 → #1069)
2026-10-19
Rank Moved
Rank dropped 28 spots (#1027 → #1055)
2026-10-14
Grade Changed
Trust grade C → D
2026-10-14
Rank Moved
Rank dropped 11 spots (#997 → #1008)
2026-10-11
Rank Moved
Rank dropped 11 spots (#975 → #986)
2026-10-09
Rank Moved
Rank dropped 14 spots (#953 → #967)
2026-10-04
Rank Moved
Rank rose 12 spots (#951 → #939)
2026-09-30
Rank Moved
Rank dropped 14 spots (#938 → #952)
2026-09-26
Grade Changed
Trust grade D → C
2026-09-26
Rank Moved
Rank rose 73 spots (#1008 → #935)
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 470 spots (#531 → #1001)
2026-09-23
HVTrust Changed
HVTrust up 8.6pts (39.0 → 47.6)
2026-09-22
Newly Listed
First tracked at rank #531
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 25 spots (#1037 → #1012)
2026-09-19
Activity Score Changed
Activity score up 6pts (45 → 51)
2026-09-18
Rank Moved
Rank rose 36 spots (#1073 → #1037)
2026-09-18
Activity Score Changed
Activity score up 6pts (39 → 45)
2026-09-12
Rank Moved
Rank dropped 15 spots (#1059 → #1074)
2026-09-09
Rank Moved
Rank dropped 18 spots (#1036 → #1054)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1025 → #1036)
2026-09-07
Rank Moved
Rank dropped 35 spots (#990 → #1025)
2026-09-06
Rank Moved
Rank dropped 13 spots (#977 → #990)
2026-09-05
Scorecard Added
OSSF Scorecard: 3.8/10
2026-09-05
Rank Moved
Rank rose 324 spots (#1301 → #977)
2026-09-05
HVTrust Changed
HVTrust up 25.7pts (19.0 → 44.7)
2026-09-02
Rank Moved
Rank dropped 17 spots (#1266 → #1283)
2026-09-01
Rank Moved
Rank dropped 14 spots (#1252 → #1266)
2026-08-31
Rank Moved
Rank dropped 16 spots (#1236 → #1252)
2026-08-30
Rank Moved
Rank dropped 18 spots (#1218 → #1236)
2026-08-29
Rank Moved
Rank dropped 15 spots (#1203 → #1218)
2026-08-28
Rank Moved
Rank dropped 17 spots (#1186 → #1203)
2026-08-27
Rank Moved
Rank dropped 12 spots (#1174 → #1186)
2026-08-26
Rank Moved
Rank dropped 52 spots (#1122 → #1174)
2026-08-24
Rank Moved
Rank dropped 12 spots (#1109 → #1121)
2026-08-19
Rank Moved
Rank rose 27 spots (#1143 → #1116)
2026-08-16
Rank Moved
Rank dropped 24 spots (#1123 → #1147)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/markifact-ai-performance-marketing.svg)](https://hvtracker.net/agents/markifact-ai-performance-marketing)
HTML:
<a href="https://hvtracker.net/agents/markifact-ai-performance-marketing"><img src="https://hvtracker.net/badge/markifact-ai-performance-marketing.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