Is the npm:@flowcontent/mcp-server MCP server safe to use?
Independent trust grade C- (70/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@flowcontent/mcp-server for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
What it offers — 7 tools · Maps & Geo
get_account_info
Get a summary of your FlowContent account: credits, plan, and configured domains
search_competitor_ads
Search the Meta Ad Library to spy on competitor ads (no ad account needed)
get_keyword_ideas
Get keyword suggestions from Google Keyword Planner (requires Google Ads connection)
get_gmb_reviews
Get Google Business Profile reviews for a location
get_analytics
Get combined Google Analytics (GA4) metrics and Search Console data
list_articles
List your FlowContent articles with optional filters
create_article
Generate an AI article (costs credits). Returns the generated article.
INFO Static analysis of npm package @flowcontent/mcp-server@0.2.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:@flowcontent/mcp-server on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.