Ghost (fanyangmeng) MCP Server

@fanyangmeng/ghost-mcp npm v0.2.0

Published by @fanyangmeng — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for using the Ghost API

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

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

  • invites_browseingests untrusted input
  • members_browseingests untrusted input
  • newsletters_browseingests untrusted input
  • offers_browseingests untrusted input
  • posts_browseingests untrusted input
  • roles_browseingests untrusted input
  • tags_browseingests untrusted input
  • tiers_browseingests untrusted input
  • users_browseingests untrusted input
  • invites_addno sensitive capability
Show 32 more tools ↓
  • invites_deleteno sensitive capability
  • members_addno sensitive capability
  • members_deleteno sensitive capability
  • members_editno sensitive capability
  • members_readno sensitive capability
  • newsletters_addno sensitive capability
  • newsletters_deleteno sensitive capability
  • newsletters_editno sensitive capability
  • newsletters_readno sensitive capability
  • offers_addno sensitive capability
  • offers_deleteno sensitive capability
  • offers_editno sensitive capability
  • offers_readno sensitive capability
  • posts_addno sensitive capability
  • posts_deleteno sensitive capability
  • posts_editno sensitive capability
  • posts_readno sensitive capability
  • roles_readno sensitive capability
  • tags_addno sensitive capability
  • tags_deleteno sensitive capability
  • tags_editno sensitive capability
  • tags_readno sensitive capability
  • tiers_addno sensitive capability
  • tiers_deleteno sensitive capability
  • tiers_editno sensitive capability
  • tiers_readno sensitive capability
  • users_deleteno sensitive capability
  • users_editno sensitive capability
  • users_readno sensitive capability
  • webhooks_addno sensitive capability
  • webhooks_deleteno sensitive capability
  • webhooks_editno 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.2.0 latest A 95/100 0 1.13.0 2026-09-06

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fanyangmeng-ghost-mcp/badge.svg)](https://mcptrustchecker.com/registry/fanyangmeng-ghost-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/fanyangmeng-ghost-mcp"><img src="https://mcptrustchecker.com/registry/fanyangmeng-ghost-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fanyangmeng-ghost-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 @fanyangmeng/ghost-mcp --online

Use the free API → How scoring works

Other implementations of Ghost 9

Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →

More in Content Management