DataForSEO MCP
NPM · @SCALABLY-IO/DATAFORSEO-MCP
DataForSEO MCP wrapper: searchable API docs plus normalized calls to the official server. 4 tools.
Available components
Last scanned (7 hours ago)
Scores higher than 55% 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 Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/client 2.0.0, reached via dataforseo-mcp-server > agents > @modelcontextprotocol/client. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 45 of 283 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 361 tokens (~90/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- CVE-2026-109841 no longer affects this package ▲ security
- CVE-2026-109924 no longer affects this package ▲ security
- CVE-2026-109869 no longer affects this package ▲ security
- 24 Oct 26 0
- CVE-2026-109924 affects this package: high ▼ security
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-111770 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
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/@scalably-io/dataforseo-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-jm63-cq47-j5jp | CVE-2026-111770 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 283 packages
| Packages resolved | 283 |
|---|---|
| Stale | 45 |
| 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 →
api_request API Request ~120
Make an authenticated request to the DataForSEO API
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Request body as JSON object or array of task objects |
| method | string | yes | HTTP method |
| noAiMode | boolean | – | Disable the .ai path suffix and return the full response schema instead of the AI-optimized subset. Can increase context size significantly. Default: false. |
| path | string | – | API path (e.g. /v3/serp/google/organic/live/regular) |
| url | string | – | Full API URL (alternative to path) |
No output schema declared.
No examples provided.
docs_index Docs Index ~45
Fetch the DataForSEO API documentation index (llms.txt), optionally filtered by section
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Filter by API section (e.g. "SERP API") |
No output schema declared.
No examples provided.
docs_list_sections Docs List Sections ~19
Return available DataForSEO API documentation section names
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
docs_search Docs Search ~84
Fetch DataForSEO API documentation from a documentation URL
| Name | Type | Req | Description |
|---|---|---|---|
| needCodeExample | boolean | – | Include multi-language code examples (PHP, Node.js, Python, C#) |
| url | string | yes | Documentation URL or path (e.g. https://docs.dataforseo.com/v3/serp/google/organic/live/regular or serp/google/organic/live/regular) |
No output schema declared.
No examples provided.
How do I install the DataForSEO MCP server?
DataForSEO MCP runs locally as an npm package, launched with npx -y @scalably-io/dataforseo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @scalably-io/dataforseo-mcp
claude mcp add io-scalably-dataforseo-mcp -- npx -y @scalably-io/dataforseo-mcp
What is the DataForSEO MCP server?
DataForSEO MCP is listed in the public MCP registry as io.scalably/dataforseo-mcp. DataForSEO MCP wrapper: searchable API docs plus normalized calls to the official server. 4 tools. This page covers its npm package (@scalably-io/dataforseo-mcp).
Is the DataForSEO MCP server safe to use?
DataForSEO MCP scores 77 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 DataForSEO MCP server expose?
DataForSEO MCP exposes 4 tools: docs_index, docs_list_sections, docs_search, api_request. Their descriptions and schemas cost roughly 268 tokens of context every time the server is loaded.
Is the DataForSEO MCP server still maintained?
DataForSEO MCP 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 DataForSEO MCP server under?
DataForSEO MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.