Mmcp.market

SEO Trends API MCP server

by trendsapi.ai·ai.trendsapi/seo·v1.0.1

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

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
New

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 (4)

write = sends, deletes, buys or posts
  • 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', '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.

Public scan report

scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it

no findings
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 396ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 35 days ago12/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

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.

Install directly

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

SEO Trends API: common questions

Is SEO Trends API MCP server safe?
Mostly: it is graded B (81/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, Claude Desktop or Cursor 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 35 days ago (2026-08-18). The latest release is v1.0.1.
Is SEO Trends API up?
100% of our last 14 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 Google Ads + Meta Ads + SEO/GEO MCP server. Compare all SEO Trends API alternatives.

Alternatives to SEO Trends API

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

All SEO Trends API alternatives →

More from trendsapi.ai