MCP.Market

SEO Trends API MCP server

online · 100% uptime
by trendsapi.ai·ai.trendsapi/seo·v1.0.2
No reviews yet

Spot keyword demand rising or fading across search and social. Free key at trendsapi.ai

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed SEO Trends API yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

SEO Trends API tools (6)

write = sends, deletes, buys or posts
  • trends___get_contextFree

    What people are posting, reading and betting about a keyword right now. Returns recent posts, videos, news stories, discussions and prediction markets per source, with engagement (views, likes, score) and top comments. Use it to explain why something is trending or what the conversation says; get_time_series and get_growth measure how much. Costs 1 request per source. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

  • trends___get_growthFree

    Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Designed for growth questions; for charting or custom math, get_time_series provides the full series. App Downloads and App Rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

  • trends___get_time_seriesFree

    Full historical series for one keyword and one source (0-100 values, plus volume when available). Suited for charting or custom math. Live 'what's trending now' boards are on get_top_trends. get_growth answers most growth questions with less data. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

  • trends___get_top_postsFree

    Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. For when the user already has a hashtag and wants the posts winning on it. get_top_trends ranks the hashtags themselves. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

  • trends___get_top_trendsFree

    Live top-trending board for exactly one feed type. No keyword. For 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Pinterest Trending by Category', 'Top Websites', 'Substack by Category', and 'TikTok Trending Hashtags by Category', category selects the board. Default sort is current rank. Use sort='rank_change' for climbers vs a prior snapshot (window 1d, 3d, 7d, 14d, or 30d). If the requested board is not in the database yet (for example a country that is not collected on the schedule), the board is fetched live. App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. App history is available via get_growth or get_time_series with source App Downloads or App Rankings and an Android bundle ID. Live boards are only available here, not via get_time_series. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

  • trends___get_usageFree

    Shows your plan, requests used this month, requests left, and when it resets. Free: does not use a request. Call it when the user asks about their limit or after a limit error.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 521ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How SEO Trends API compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 769 SEO servers
Tools
6
the typical SEO server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote SEO server answers 100%
Response time
177 ms
faster than 70% of 536 SEO servers

What its tools let an agent do: 6 read

Release history: 2 versions in the registry since 2026-08-18, latest 2026-10-21, typically one every 64 days.

Install SEO Trends API in Claude Code, Cursor or VS Code

claude mcp add --transport http seo https://seo.api.trendsapi.ai/mcp
Add to Cursor

What the publisher says

From the SEO Trends API repository's README, as published. We do not edit it. Read it on GitHub

Remote MCP server

Hosted MCP at https://api.trendsapi.ai/mcp. Same three operations and catalogs as REST. Token: trendsapi.ai/#get-key.

REST contract: trendsapi-ai/trendsapi.

Tools

Sources, feeds, and keyword formats: hub keyword sources and live feeds.

app downloads / app rankings still need an Android bundle ID (com.openai.chatgpt).

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "trend-feeds": {
      "url": "https://api.trendsapi.ai/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

VS Code

.vscode/mcp.json:

{
  "servers": {
    "trend-feeds": {
      "type": "http",
      "url": "https://api.trendsapi.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Claude Desktop

{
  "mcpServers": {
    "trend-feeds": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.trendsapi.ai/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_TOKEN" }
    }
  }
}

Claude.ai: Settings → Connectors → Add custom connector → https://api.trendsapi.ai/mcp.

No local production server in this repo.

License

MIT. See LICENSE.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-03restoreB → Ascore 88

SEO Trends API: common questions

Is SEO Trends API MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the SEO Trends API safety report
How do I install SEO Trends API?
It runs remotely at seo.api.trendsapi.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does SEO Trends API need an API key?
Yes. The registry entry asks for Authorization.
Is SEO Trends API maintained?
The last commit was 2 days ago (2026-11-03). The latest release is v1.0.2.
Is SEO Trends API up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of SEO Trends API?
Servers from other publishers that do the same job: X (Twitter) Trends MCP server, Cite42 MCP server and SEO Skill MCP server.
How does SEO Trends API compare with other SEO MCP servers?
safety score 88/100 (higher than 80% of 769 SEO servers); tools 6 (the typical SEO server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to SEO Trends API

Same job from other publishers: the closest match first, then the best rated.

  • X (Twitter) Trends MCP
    Twitter (X) trends over time, with growth for any keyword. Free key at trendsmcp.ai
    More from trendsmcp.ai →
    A
  • Cite42
    AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers.
    A
  • SEO Skill
    Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
    A
  • DispatchSEO
    Open-source SEO manager for coding agents: keyword research, content PRs, rank + Search Console.
    A
  • bisibility
    Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents.
    A

More from trendsapi.ai →