Ghost Publisher MCP Server
ghost-publisher-mcp
npm
v0.10.1
Source verified
Published by blogfactoryhq — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Local-first MCP server for safe Ghost posts, Pages, scheduling, images, and publishing.
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 − 3 = 97. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
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 (dist/setup.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/setup.js:1`): 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: spawnSync } from 'node:child_process'; import { randomUUID } from 'node:crypto'; import { constants } from 'node:fs'; i
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 dist/setup.js
Tools 20
Each tool and what it can reach — statically extracted from the published source.
get_pageingests untrusted inputapply_change_setno sensitive capabilityaudit_contentno sensitive capabilitycheck_connectionno sensitive capabilitycheck_live_pagesno sensitive capabilitycheck_live_postsno sensitive capabilitycheck_site_healthno sensitive capabilitycreate_draftsno sensitive capabilitycreate_page_draftsno sensitive capabilityget_postno sensitive capability
Show 10 more tools ↓
list_authorsno sensitive capabilitylist_pagesno sensitive capabilitylist_postsno sensitive capabilitylist_tagsno sensitive capabilityplan_scheduleno sensitive capabilitypreview_changesno sensitive capabilityschedule_postsno sensitive capabilitytrigger_deployno sensitive capabilityunschedule_postsno sensitive capabilityupload_imageno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 4
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.10.1 latest |
A 97/100 | 1 | 1.13.0 | 2026-09-06 |
v0.10.0 |
A 97/100 | 1 | 1.13.0 | 2026-08-25 |
v0.7.0 |
A 97/100 | 1 | 1.12.1 | 2026-08-16 |
v0.4.1 |
A 97/100 | 1 | 1.12.1 | 2026-08-02 |
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.
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 ghost-publisher-mcp --onlineMore in Content Management
Apify MCP Server
Model Context Protocol (MCP) Server for the *@inkeep/agents-mcp* API.
Medicare spending, chronic conditions, hospital quality, readmissions, and enrollment
Public read-only MCP for products, frameworks, guides, methodology, and blog metadata.
Community-maintained MCP server for Atlassian Confluence Data Center. Not affiliated with Atlassian.
MCP server for Contentful Content Management API integration