MCP.Market

Wikipedia Trends MCP server

online · 100% uptime
by trendsmcp.ai·ai.trendsmcp/wikipedia·v1.0.7

Wikipedia page views over time, with growth for any article topic. Free key at trendsmcp.ai

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

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Wikipedia Trends MCP yet.

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

Wikipedia Trends MCP 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 531ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 65 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Wikipedia Trends MCP compares

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

Safety score
84/100
higher than 68% of 48,255 servers
Tools
6
the typical server has 7
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 server answers 100%
Response time
179 ms
faster than 67% of 30,031 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 Wikipedia Trends MCP in Claude Code, Cursor or VS Code

claude mcp add --transport http wikipedia https://wikipedia.api.trendsmcp.ai/mcp
Add to Cursor

What the publisher says

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

<!-- mcp-name: ai.trendsmcp/wikipedia-trends-mcp -->

Wikipedia Trends MCP

Live trend data for AI agents. Google, TikTok, YouTube, Amazon, Reddit, and 30+ other sources. One MCP connection, one API key.

Get a free API key · Docs · Pricing · Data sources · PyPI · Glama

You: Using TrendsMCP, compare 6-month growth for GLP-1 on Google, TikTok, and Amazon.

Agent: Google Search  +84%
       TikTok         +212%
       Amazon         +61%

Three tools. Normalized 0–100 where the pipeline supports it. No per-platform keys. No scraping on your side.

Quick install

Same four clients as the site hero. Get a free key first (100 req/mo). Claude and ChatGPT sign you in with OAuth. Cursor and VS Code: click, then put your key from /account if the deeplink used a placeholder.

Then ask: Using TrendsMCP, what's trending on Google right now?

Tools · Sources · Feeds · REST · Install in other clients

What this is

Hosted MCP at https://api.trendsmcp.ai/mcp. Same Bearer key for POST https://api.trendsmcp.ai/api. This repo also has a stdio adapter for Glama and local hosts.

Shortened. The full README is on GitHub.

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

Grade history

  • 2026-11-03downgradeA → Bscore 84

Wikipedia Trends MCP: common questions

Is Wikipedia Trends MCP server safe?
Mostly: it is graded B (84/100). Read the Wikipedia Trends MCP safety report
How do I install Wikipedia Trends MCP?
It runs remotely at wikipedia.api.trendsmcp.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 Wikipedia Trends MCP need an API key?
Yes. The registry entry asks for Authorization.
Is Wikipedia Trends MCP maintained?
The last commit was 66 days ago (2026-08-30). The latest release is v1.0.7.
Is Wikipedia Trends MCP up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Wikipedia Trends MCP compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from trendsmcp.ai →