Fetchserp MCP Server
fetchserp-mcp-server
npm
v1.0.5
Published by fetchserp — 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.
A Model Context Protocol (MCP) server that provides access to FetchSERP API for SEO analysis, SERP data, web scraping, and keyword research. Supports both stdio and HTTP transport modes.
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 10
high Tool "scrape_webpage_js" exposes command/code executionMTC-CAP-001
Tool "scrape_webpage_js" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool scrape_webpage_js
high Tool "scrape_webpage_js_proxy" exposes command/code executionMTC-CAP-001
Tool "scrape_webpage_js_proxy" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool scrape_webpage_js_proxy
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([scrape_webpage, scrape_domain, scrape_webpage_js, scrape_webpage_js_proxy]) co-exist with external-action tools ([scrape_webpage_js, scrape_webpage_js_proxy]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [scrape_webpage, scrape_domain, scrape_webpage_js, scrape_webpage_js_proxy] → sinks [scrape_webpage_js, scrape_webpage_js_proxy]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow scrape_webpage → scrape_webpage_js
medium Unconstrained URL/host parameter "url" on "scrape_webpage"MTC-CAP-007
Tool "scrape_webpage" 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 scrape_webpage · inputSchema.properties.url
medium Unconstrained URL/host parameter "url" on "scrape_webpage_js"MTC-CAP-007
Tool "scrape_webpage_js" 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 scrape_webpage_js · inputSchema.properties.url
medium Unconstrained URL/host parameter "url" on "scrape_webpage_js_proxy"MTC-CAP-007
Tool "scrape_webpage_js_proxy" 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 scrape_webpage_js_proxy · inputSchema.properties.url
medium Unconstrained command parameter "js_script" on "scrape_webpage_js"MTC-CAP-006
Tool "scrape_webpage_js" takes a command-shaped parameter "js_script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool scrape_webpage_js · inputSchema.properties.js_script
medium Unconstrained command parameter "js_script" on "scrape_webpage_js_proxy"MTC-CAP-006
Tool "scrape_webpage_js_proxy" takes a command-shaped parameter "js_script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool scrape_webpage_js_proxy · inputSchema.properties.js_script
low Mutating tool "scrape_webpage_js" declares no destructiveHintMTC-CAP-005
Tool "scrape_webpage_js" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool scrape_webpage_js
low Mutating tool "scrape_webpage_js_proxy" declares no destructiveHintMTC-CAP-005
Tool "scrape_webpage_js_proxy" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool scrape_webpage_js_proxy
Tools 24
Each tool and what it can reach — statically extracted from the published source.
scrape_webpage_jsingests untrusted inputruns code / shellscrape_webpage_js_proxyingests untrusted inputruns code / shellscrape_domainingests untrusted inputscrape_webpageingests untrusted inputcheck_page_indexationno sensitive capabilityFetchSERP MCP Serverno sensitive capabilitygenerate_social_contentno sensitive capabilitygenerate_wordpress_contentno sensitive capabilityget_backlinksno sensitive capabilityget_domain_emailsno sensitive capability
Show 14 more tools ↓
get_domain_infono sensitive capabilityget_domain_rankingno sensitive capabilityget_keywords_search_volumeno sensitive capabilityget_keywords_suggestionsno sensitive capabilityget_long_tail_keywordsno sensitive capabilityget_moz_analysisno sensitive capabilityget_playwright_mcpno sensitive capabilityget_serp_ai_modeno sensitive capabilityget_serp_htmlno sensitive capabilityget_serp_resultsno sensitive capabilityget_serp_textno sensitive capabilityget_user_infono sensitive capabilityget_webpage_ai_analysisno sensitive capabilityget_webpage_seo_analysisno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (24 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 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.5 latest |
A 93/100 | 10 | 1.13.0 | 2026-09-07 |
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 fetchserp-mcp-server --onlineMore in Web, Search & Scraping
Agent IP: MCP server with patents search tools
MCP server for searching the Agent Almanac — the public catalog of 9,000+ Model Context Protocol servers. Find, install, and discover MCP servers from inside Claude Desktop, Cursor, Continue, Zed, or any MCP-aware agent.
Search agents & MCP servers by capability, with daily-observed pricing, liveness and market data.
Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.
Airframe MCP Client - Connect agents to Airframe's product intelligence
Amazon product search demand over time, with growth for any keyword. Free key at trendsmcp.ai