Just Facebook MCP Server

just-facebook-mcp PyPI v0.1.0

Published by livia-zaharia — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for automating and managing interactions on a Facebook Page using the Facebook Graph API

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Shell/command execution in packaging/dev tooling (scripts/build_and_publish.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/build_and_publish.py:18`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: command}") result = subprocess.run(command, shell=True, check=check, capture_output=True, text=True) if result.s

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/build_and_publish.py

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • get_page_fan_countingests untrusted input
  • get_page_postsingests untrusted input
  • get_post_clicksingests untrusted input
  • get_post_engaged_usersingests untrusted input
  • get_post_impressionsingests untrusted input
  • get_post_impressions_organicingests untrusted input
  • get_post_impressions_paidingests untrusted input
  • get_post_impressions_uniqueingests untrusted input
  • get_post_insightsingests untrusted input
  • get_post_reactions_anger_totalingests untrusted input
Show 20 more tools ↓
  • get_post_reactions_haha_totalingests untrusted input
  • get_post_reactions_like_totalingests untrusted input
  • get_post_reactions_love_totalingests untrusted input
  • get_post_reactions_sorry_totalingests untrusted input
  • get_post_reactions_wow_totalingests untrusted input
  • delete_commentno sensitive capability
  • delete_comment_from_postno sensitive capability
  • delete_postno sensitive capability
  • filter_negative_commentsno sensitive capability
  • get_number_of_commentsno sensitive capability
  • get_number_of_likesno sensitive capability
  • get_post_commentsno sensitive capability
  • get_post_share_countno sensitive capability
  • get_post_top_commentersno sensitive capability
  • post_image_to_facebookno sensitive capability
  • post_to_facebookno sensitive capability
  • reply_to_commentno sensitive capability
  • schedule_postno sensitive capability
  • send_dm_to_userno sensitive capability
  • update_postno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.0 latest A 96/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/just-facebook-mcp/badge.svg)](https://mcptrustchecker.com/registry/just-facebook-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/just-facebook-mcp"><img src="https://mcptrustchecker.com/registry/just-facebook-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/just-facebook-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan just-facebook-mcp --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow