Semrush
NPM · @PIPEWORX/MCP-SEMRUSH · 2 COMPONENTS
Semrush MCP Pack — SEO analytics via the Semrush Analytics API.
Available components
Last scanned (9 hours ago)
Scores higher than 72% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-semrush). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1258 tokens (~209/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-semrush@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-semrush |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-semrush/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692343957 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4f420241807d99a6a3e2aa6879bc8e0fba0b6a7fcd7a8850008a72fe74b1b2342e3b405b6d0ca630f7f7e103144f8fc85c2855ed6e6d15e3045eae48b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
backlinks_overview ~197
Backlinks summary for a domain or URL (Semrush type=backlinks_overview). Returns parsed rows with columns: target, target_type, total (total backlinks), domains_num (referring domains), urls_num (referring URLs), ips_num (referring IPs), follows_num (dofollow), nofollows_num, texts_num, images_num, score (authority score). Note: backlinks reports are not regional — there is no `database` param. Consumes your Semrush API units.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units. |
| target | string | yes | Domain or URL to analyze, e.g. "apple.com". |
| target_type | string | – | One of "root_domain", "domain" (subdomain), or "url". Default root_domain. |
No output schema declared.
No examples provided.
domain_organic_keywords ~242
Top organic search keywords a domain ranks for (Semrush type=domain_organic). Returns parsed rows with columns: Ph (keyword phrase), Po (current position), Pp (previous position), Nq (search volume), Cp (CPC), Ur (ranking URL), Tr (traffic %), Co (competition), Nr (number of results). Consumes your Semrush API units.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units. |
| database | string | – | 2-letter Semrush regional database (e.g. us, uk, de, fr, es, ca, au). Default us. |
| display_limit | number | – | Max keywords to return (default Semrush 10000; pass a small value like 50). |
| display_sort | string | – | Sort order, e.g. "tr_desc" (traffic), "nq_desc" (volume), "po_asc" (position). Optional. |
| domain | string | yes | Domain to analyze, e.g. "apple.com". |
No output schema declared.
No examples provided.
domain_overview ~202
Domain overview (Semrush type=domain_ranks): high-level SEO/PPC summary for a domain. Returns parsed rows with columns: Db (database), Dn (domain), Rk (Semrush rank), Or (organic keywords count), Ot (organic traffic), Oc (organic traffic cost), Ad (adwords/paid keywords count), At (paid traffic), Ac (paid traffic cost). Consumes your Semrush API units.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units. |
| database | string | – | 2-letter Semrush regional database (e.g. us, uk, de, fr, es, ca, au). Default us. |
| display_limit | number | – | Max rows to return. |
| domain | string | yes | Domain to analyze, e.g. "apple.com" (no scheme). |
No output schema declared.
No examples provided.
domain_paid_keywords ~199
Paid (AdWords/PPC) keywords a domain bids on (Semrush type=domain_adwords). Returns parsed rows with columns: Ph (keyword phrase), Po (ad position), Nq (search volume), Cp (CPC), Ur (landing page URL), Tg (traffic), Tc (traffic cost), Co (competition), Nr (number of results). Consumes your Semrush API units.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units. |
| database | string | – | 2-letter Semrush regional database (e.g. us, uk, de, fr, es, ca, au). Default us. |
| display_limit | number | – | Max keywords to return (pass a small value like 50). |
| domain | string | yes | Domain to analyze, e.g. "apple.com". |
No output schema declared.
No examples provided.
keyword_overview ~176
Keyword overview (Semrush type=phrase_this): search metrics for a single keyword phrase. Returns parsed rows with columns: Ph (phrase), Nq (search volume), Cp (CPC), Co (competition 0-1), Nr (number of organic results), Td (trend, last 12 months as |-separated values). Consumes your Semrush API units.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units. |
| database | string | – | 2-letter Semrush regional database (e.g. us, uk, de, fr, es, ca, au). Default us. |
| phrase | string | yes | Keyword phrase to look up, e.g. "running shoes". |
No output schema declared.
No examples provided.
organic_competitors ~189
Organic search competitors for a domain (Semrush type=domain_organic_organic). Returns parsed rows with columns: Dn (competitor domain), Cr (competition level), Np (common keywords), Or (competitor organic keywords), Ot (competitor organic traffic), Oc (organic cost). Consumes your Semrush API units.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your own Semrush API key (BYO). Passed to Semrush as the `key` query param. Consumes your Semrush API units. |
| database | string | – | 2-letter Semrush regional database (e.g. us, uk, de, fr, es, ca, au). Default us. |
| display_limit | number | – | Max competitors to return (pass a small value like 25). |
| domain | string | yes | Domain to find competitors for, e.g. "apple.com". |
No output schema declared.
No examples provided.
How do I install the Semrush MCP server?
Semrush runs locally as an npm package, launched with npx -y @pipeworx/mcp-semrush. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-semrush
claude mcp add pipeworx-io-semrush -- npx -y @pipeworx/mcp-semrush
What is the Semrush MCP server?
Semrush is an MCP server listed in the public MCP registry as io.github.pipeworx-io/semrush. Semrush MCP Pack, SEO analytics via the Semrush Analytics API. This page covers its npm package (@pipeworx/mcp-semrush).
Is the Semrush MCP server safe to use?
Semrush scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Semrush MCP server expose?
Semrush exposes 6 tools: domain_overview, domain_organic_keywords, domain_paid_keywords, keyword_overview, backlinks_overview, organic_competitors. Their descriptions and schemas cost roughly 1,205 tokens of context every time the server is loaded.
Is the Semrush MCP server still maintained?
Semrush is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Semrush MCP server under?
Semrush declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.