Doomscrollr MCP Server

@doomscrollr/mcp-server npm v1.1.2 Source verified

Published by doomscrollr — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

DOOMSCROLLR MCP server — AI agents build owned-audience websites, affiliate storefronts, product drops, newsletters, tickets, and subscriber capture for the audience layer of the AI agent world.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 = 97/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 − 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:

PointsAdoption-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 2

medium Unconstrained URL/host parameter "url" on "doomscrollr_import_shopify_products"MTC-CAP-007

Tool "doomscrollr_import_shopify_products" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool doomscrollr_import_shopify_products · inputSchema.properties.url

medium Dynamic module load from a non-literal (dist/http.js)MTC-SRC-005

In the server's implementation (`dist/http.js:77`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: generatedServerCard = require(cardPath); } catch { try { // eslint-disable-next-line @typescript-eslint/no

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/http.js

Tools 55

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

  • doomscrollr_connect_rssingests untrusted input
  • doomscrollr_disconnect_rssingests untrusted input
  • doomscrollr_get_curation_themeingests untrusted input
  • doomscrollr_get_n8n_templatesingests untrusted input
  • doomscrollr_import_shopify_productsingests untrusted input
  • doomscrollr_publish_postingests untrusted input
  • doomscrollr_rss_statusingests untrusted input
  • doomscrollr_scrape_shopify_productsingests untrusted input
  • doomscrollr_scrape_url_productsingests untrusted input
  • doomscrollr_add_subscriberno sensitive capability
Show 45 more tools ↓
  • doomscrollr_apply_style_presetno sensitive capability
  • doomscrollr_bulk_delete_postsno sensitive capability
  • doomscrollr_bulk_delete_productsno sensitive capability
  • doomscrollr_bulk_delete_subscribersno sensitive capability
  • doomscrollr_bulk_update_postsno sensitive capability
  • doomscrollr_bulk_update_productsno sensitive capability
  • doomscrollr_bulk_update_subscribersno sensitive capability
  • doomscrollr_buy_domainno sensitive capability
  • doomscrollr_connect_domainno sensitive capability
  • doomscrollr_connect_instagramno sensitive capability
  • doomscrollr_connect_pinterestno sensitive capability
  • doomscrollr_create_contact_pageno sensitive capability
  • doomscrollr_create_pageno sensitive capability
  • doomscrollr_create_productno sensitive capability
  • doomscrollr_create_worldno sensitive capability
  • doomscrollr_delete_postno sensitive capability
  • doomscrollr_delete_productno sensitive capability
  • doomscrollr_delete_subscriberno sensitive capability
  • doomscrollr_disconnect_domainno sensitive capability
  • doomscrollr_disconnect_pinterestno sensitive capability
  • doomscrollr_domain_statusno sensitive capability
  • doomscrollr_export_audience_csvno sensitive capability
  • doomscrollr_get_embed_codeno sensitive capability
  • doomscrollr_get_profileno sensitive capability
  • doomscrollr_get_settingsno sensitive capability
  • doomscrollr_get_zapier_templatesno sensitive capability
  • doomscrollr_import_url_productsno sensitive capability
  • doomscrollr_list_postsno sensitive capability
  • doomscrollr_list_productsno sensitive capability
  • doomscrollr_list_subscribersno sensitive capability
  • doomscrollr_pinterest_statusno sensitive capability
  • doomscrollr_post_shopmy_productsno sensitive capability
  • doomscrollr_prepare_user_questionsno sensitive capability
  • doomscrollr_publish_image_postno sensitive capability
  • doomscrollr_publish_polymarket_postno sensitive capability
  • doomscrollr_remove_subscriberno sensitive capability
  • doomscrollr_search_domainsno sensitive capability
  • doomscrollr_search_pinterestno sensitive capability
  • doomscrollr_search_pinterest_and_postno sensitive capability
  • doomscrollr_set_curation_themeno sensitive capability
  • doomscrollr_top_liked_postsno sensitive capability
  • doomscrollr_update_postno sensitive capability
  • doomscrollr_update_productno sensitive capability
  • doomscrollr_update_settingsno sensitive capability
  • doomscrollr_update_subscriberno 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
v1.1.2 latest A 97/100 2 1.13.0 2026-09-09

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

Use the free API → How scoring works

More in Developer Tools