dataforseo

An MCP server that connects coding agents to the DataForSEO API, a service providing search-engine and marketing data. It can browse the API documentation and make authenticated requests, using configured modules such as rankings, keywords, page analysis, backlinks, business data, and AI optimization.

In plain words
What is it for?
Use it to look up DataForSEO capabilities and request search, keyword, on-page, backlink, domain, business, content, and AI-visibility data when the required credentials and modules are configured.
Why use it?
It provides one connection for retrieving external SEO data instead of requiring each analysis to implement its own API access.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add mcp/bestlemoon/codex-seo/dataforseo
Clone the repo
git clone --depth 1 https://github.com/BestLemoon/codex-seo

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

dataforseo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 15 lines

What it actually says

{
  "dataforseo": {
    "command": "npx",
    "args": [
      "-y",
      "dataforseo-mcp-server"
    ],
    "env": {
      "DATAFORSEO_USERNAME": "${DATAFORSEO_USERNAME}",
      "DATAFORSEO_PASSWORD": "${DATAFORSEO_PASSWORD}",
      "ENABLED_MODULES": "SERP,KEYWORDS_DATA,ONPAGE,DATAFORSEO_LABS,BACKLINKS,DOMAIN_ANALYTICS,BUSINESS_DATA,CONTENT_ANALYSIS,AI_OPTIMIZATION",
      "FIELD_CONFIG_PATH": "./extensions/dataforseo/field-config.json"
    }
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 15 lines scan A 709aec021dfb

Subscribe to this mod's changes

dataforseo is an MCP server published in the GitHub repository BestLemoon/codex-seo (9 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.