Keyword Research API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 27, 2026

SEO keyword research with Google Suggest, intent scoring, long-tail discovery. x402.

VerifiedSSEWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for SEO keyword research: Google Suggest ideas, related queries, long-tail keywords and search intent, paid per call via x402.

What you can do
  • Research keywords for a seed phrase, returning Google autocomplete suggestions, related queries, long-tail keywords and an intent classification as JSON.
  • Same research available through a GET or a POST variant of the single keyword research tool.
  • Intended for content planning, topic clusters, content gap analysis and competitive keyword work.
When to use it
Useful when an assistant is drafting blog posts or SEO content strategy and needs keyword ideas and intent data for a topic. It is not for page audits, content extraction or domain intelligence, which the README points to other services for.
Requirements
A remote MCP client pointed at the hosted endpoint; nothing to install locally. No API key or signup, but each call is paid in USDC on Base L2 through the x402 protocol, so the client needs an x402-capable wallet or payment flow. Network access to the provider's domain.
Before you install
Every call costs money (listed at $0.02 per request) in USDC on Base, so automated loops can spend funds; set spending limits. Payment is handled by a wallet or x402 client, and the provider names Coinbase CDP and PayAI as facilitators. The seed queries you send go to the provider and to Google Suggest.

Installation

In SourceWeft

  1. Open Keyword Research API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fkeyword-research/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "keyword-research-api": {
      "type": "sse",
      "url": "https://keyword-research.api.klymax402.com/mcp"
    }
  }
}

README

Keyword Research API

[MCP Server] [x402] [License: MIT]

SEO keyword research -- Google Suggest, intent classification, long-tail discovery, related queries. Content planning. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "keyword-research": {      "url": "https://keyword-research.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl "https://keyword-research.api.klymax402.com/api/keywords?query=..."# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
seo_research_keywordsGET/api/keywords$0.02Research keywords with Google autocomplete suggestions, related queries, and intent classification
seo_research_keywordsPOST/api/keywords$0.02Research keywords with Google autocomplete suggestions, related queries, and intent classification (POST variant)

seo_research_keywords

Use this when you need keyword ideas, SEO research, or content planning data for a topic. Returns keyword suggestions and intent data in JSON.

Parameters

NameTypeRequiredDescription
querystringyesThe seed keyword or phrase to research (e.g. 'bitcoin trading', 'best crm software')

Example response:

json
{"query":"bitcoin trading","suggestions":["bitcoin trading platform","bitcoin trading bot","bitcoin trading for beginners"],"relatedQueries":{"vs":["bitcoin trading vs investing"],"howTo":["how to start bitcoin trading"]},"longTailKeywords":["best bitcoin trading app 2026","bitcoin trading strategy for beginners"],"searchIntent":"commercial","totalKeywords":47}

When to use: writing blog posts, FOR SEO content strategy, topic cluster planning, content gap analysis, and competitive keyword research.

Not for: page SEO audit (use seo_audit_page), content extraction (use web_scrape_to_markdown), domain intelligence (use domain_lookup_intelligence).

seo_research_keywords

Use this when you need keyword ideas, SEO research, or content planning data for a topic. Returns keyword suggestions and intent data in JSON. POST variant of seo_research_keywords -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
querystringyesThe seed keyword or phrase to research (e.g. 'bitcoin trading', 'best crm software')

Example response:

json
{"query":"bitcoin trading","suggestions":["bitcoin trading platform","bitcoin trading bot","bitcoin trading for beginners"],"relatedQueries":{"vs":["bitcoin trading vs investing"],"howTo":["how to start bitcoin trading"]},"longTailKeywords":["best bitcoin trading app 2026","bitcoin trading strategy for beginners"],"searchIntent":"commercial","totalKeywords":47}

When to use: writing blog posts, FOR SEO content strategy, topic cluster planning, content gap analysis, and competitive keyword research.

Not for: page SEO audit (use seo_audit_page), content extraction (use web_scrape_to_markdown), domain intelligence (use domain_lookup_intelligence).

Example agent prompts

  • "Keyword ideas, SEO research, or content planning data for a topic"
  • "Keyword ideas, SEO research, or content planning data for a topic"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit d84a569

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts