Sprout (oliverames) MCP Server
@oliverames/sprout-mcp-server
npm
v1.3.2
Published by @oliverames — 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 Sprout Social API
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 − 7 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — 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
high Shell/command execution in server code (dist/op-fallback.js)MTC-SRC-002
In the server's implementation (`dist/op-fallback.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: ecFileSync } from "node:child_process"; /** * If the given env var is empty, attempt to resolve it from 1Password CLI.
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/op-fallback.js
Tools 28
Each tool and what it can reach — statically extracted from the published source.
sprout_start_multipart_uploadingests untrusted inputsprout_analyze_listening_trendsno sensitive capabilitysprout_auth_statusno sensitive capabilitysprout_compare_profilesno sensitive capabilitysprout_compile_performance_reportno sensitive capabilitysprout_complete_multipart_uploadno sensitive capabilitysprout_continue_multipart_uploadno sensitive capabilitysprout_create_draft_postno sensitive capabilitysprout_draft_campaignno sensitive capabilitysprout_get_all_messagesno sensitive capability
Show 18 more tools ↓
sprout_get_casesno sensitive capabilitysprout_get_listening_messagesno sensitive capabilitysprout_get_listening_metricsno sensitive capabilitysprout_get_messagesno sensitive capabilitysprout_get_postno sensitive capabilitysprout_get_post_analyticsno sensitive capabilitysprout_get_profile_analyticsno sensitive capabilitysprout_list_customersno sensitive capabilitysprout_list_groupsno sensitive capabilitysprout_list_profilesno sensitive capabilitysprout_list_queuesno sensitive capabilitysprout_list_tagsno sensitive capabilitysprout_list_teamsno sensitive capabilitysprout_list_topicsno sensitive capabilitysprout_list_usersno sensitive capabilitysprout_schedule_campaign_queueno sensitive capabilitysprout_triage_support_casesno sensitive capabilitysprout_upload_mediano sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (28 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 2
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 |
|---|---|---|---|---|
v1.3.2 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
v1.3.1 |
A 93/100 | 1 | 1.12.1 | 2026-08-12 |
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 @oliverames/sprout-mcp-server --onlineOther implementations of Sprout 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Marketing & Social
Official Abyssfall game info, newsletter double opt-in, and merch reservation tools.
AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
Google AdSense MCP Server - Monitor earnings, reports, and account health via Claude/AI
Operational empathy for technical founders + PE/VC operators navigating high-stakes B2B interactions. 28 MCP tools + CLI: ICP scoring, persona simulation, battlecards, deal classification, prospect discovery, investor matching, founder wellness, plus mark
MCP server for Bing Webmaster Tools — SEO site management, URL submission, sitemaps, stats, keywords
MCP (Model Context Protocol) server that helps AI agents use Primer Brand (@primer/react-brand) correctly when building GitHub marketing and landing pages.