Is Meta MCP safe to use?

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

What is the trust score for Meta MCP?

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

Meta MCP

mikusnuz/meta-mcp

MCP server for Instagram Graph API, Threads API & Meta platform — 57 tools with Graph API v25.0

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 2.3 / 10

Provenance None

Signed commits 0%

Last push 28d ago

Compare Meta MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Meta MCP scores 47.1/100 (Grade D), ranked #1018 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 2.3/10; recent commits are unsigned; last pushed 2026-08-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Meta MCP compares in MCP Servers

#595 MCP Brasil 47.2 +0.1
#596 UnrealMCP — AI Bridge for Unreal Engine 5 47.1 ±0
#597 Meta MCP 47.1 this agent
#598 Arduino MCP Server 47.0 −0.1
#599 Kylas CRM 46.9 −0.2

Bars show each HVTrust score; the tick marks Meta MCP’s 47.1.

Where the 47.1 comes from

HVTrust dimensions vs the MCP Servers average

47.1 / 100 · 100.0% confidence

Meta MCP MCP Servers average (775 agents)

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

2.9 / 25

7.4 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

10.5 / 17

1.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.3 / 20

0.8 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.6 / 20

0.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-25

Rank Moved

Rank dropped 11 spots (#1006 → #1017)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 150 spots (#1157 → #1007)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.3/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 Meta MCP View MCP Servers Report missing data

38.3

Activity sub-score · out of 100

#597

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-08-29

28 days ago

Commits (4 wk)

Downloads (7d)

258

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1017

Analysis

Activity Inputs

38.3 / 100

StarsRepository reach

8.5 / 30

FreshnessLast push recency

21.1 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

4.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.3 / 10

OpenSSF Scorecard · scanned Sep 12, 2026 (refresh pending)

Signed Commits

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 5

Packaging -1

Pinned-Dependencies 5

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 1

Common questions about Meta MCP

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

No published build provenance is currently detected for Meta 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 Meta MCP have an OpenSSF Scorecard?

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

Maintained. Last push was 28 days ago.

What license does Meta MCP use?

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

Are Meta MCP's commits signed?

0% of the last 100 commits to Meta 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

high confidence

Implemented

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

Maintain Meta MCP?

For maintainers

HVTrust scores Meta 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-25

Rank Moved

Rank dropped 11 spots (#1006 → #1017)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 150 spots (#1157 → #1007)

2026-09-23

HVTrust Changed

HVTrust up 26.7pts (20.5 → 47.2)

2026-09-22

Newly Listed

First tracked at rank #1157

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 10 spots (#1000 → #1010)

2026-09-12

Rank Moved

Rank dropped 12 spots (#979 → #991)

2026-09-11

Rank Moved

Rank dropped 13 spots (#966 → #979)

2026-09-09

Rank Moved

Rank dropped 38 spots (#929 → #967)

2026-09-08

Rank Moved

Rank dropped 16 spots (#913 → #929)

2026-09-07

Rank Moved

Rank dropped 44 spots (#869 → #913)

2026-09-05

Grade Changed

Trust grade C → D

2026-09-05

Rank Moved

Rank dropped 115 spots (#755 → #870)

2026-09-05

Activity Score Changed

Activity score down 5pts (46 → 41)

2026-09-04

Rank Moved

Rank dropped 31 spots (#724 → #755)

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 389 spots (#1113 → #724)

2026-09-03

HVTrust Changed

HVTrust up 17.1pts (33.9 → 51.0)

2026-09-02

Rank Moved

Rank dropped 46 spots (#1067 → #1113)

2026-09-01

Scorecard Added

OSSF Scorecard: 3.3/10

2026-09-01

Rank Moved

Rank rose 179 spots (#1246 → #1067)

2026-09-01

HVTrust Changed

HVTrust up 14.4pts (19.6 → 34.0)

2026-08-31

Rank Moved

Rank dropped 18 spots (#1228 → #1246)

2026-08-30

Rank Moved

Rank dropped 23 spots (#1205 → #1228)

2026-08-29

Rank Moved

Rank dropped 21 spots (#1184 → #1205)

2026-08-27

Rank Moved

Rank dropped 11 spots (#1180 → #1191)

2026-08-26

Rank Moved

Rank dropped 46 spots (#1134 → #1180)

2026-08-24

Rank Moved

Rank dropped 11 spots (#1121 → #1132)

2026-08-16

Rank Moved

Rank dropped 27 spots (#1103 → #1130)

2026-08-10

Rank Moved

Rank dropped 62 spots (#1039 → #1101)

2026-08-08

Newly Listed

First tracked at rank #1037

GitHub → npm: @mikusnuz/meta-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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