MCP.Market

Wikipedia Trends API MCP server

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

Wikipedia page view trends for any topic over time. Free key at trendsapi.ai

B84/100grade B
Write a reviewRun it
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 API yet.

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

Wikipedia 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 586ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 77 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 API 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
138 ms
faster than 75% 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 API in Claude Code, Cursor or VS Code

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

What the publisher says

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

Wikipedia page-view trends API

Wikipedia article attention via the Trends API. History, growth, and live trending pages as 0-100 scores.

Key: trendsapi.ai/#get-key. HTTP contract and every source: trendsapi-ai/trendsapi.

Authentication

pip install trendsapi-wikipedia
export TRENDSAPI_KEY=your_key

Python 3.9+. Same key as the HTTP API.

from trendsapi_wikipedia import TrendsAPI

client = TrendsAPI()                    # TRENDSAPI_KEY
# client = TrendsAPI(api_key="YOUR_KEY")

Keyword helpers default to source: "wikipedia". Pass source= to hit any other platform with the same client. Official full client (every source, no preset): trendsapi.

Methods

source is lowercase (wikipedia). type is exact (Wikipedia Trending). Mixing them is a 400.

from trendsapi_wikipedia import TrendsAPI

client = TrendsAPI()                    # TRENDSAPI_KEY
# client = TrendsAPI(api_key="YOUR_KEY")

series = client.get_time_series("large language model")
print(series[-1].date, series[-1].value)

growth = client.get_growth("large language model", percent_growth=["3M", "12M"])
print(growth.results[0].growth, growth.results[0].direction)

hot = client.get_live(limit=10)
print(hot.data)                         # [[1, "..."], ...]

gettimeseries

points = client.get_time_series("large language model")

Each point:

Python returns list[TrendsDataPoint]. Use .date and .value, not ["date"]. JS returns the same fields as object properties.

get_growth

g = client.get_growth("large language model", percent_growth=["12M", "3M", "YTD"])
print(g.results[0].growth, g.results[0].direction)

percent_growth default: ["12M"]. Presets: 7D 14D 30D 1M 2M 3M 6M 9M 12M/1Y 18M 24M/2Y 36M/3Y 48M 60M/5Y MTD QTD YTD. Custom: {"name": "Launch", "recent": "2024-06-01", "baseline": "2024-01-01"}.

Several windows still count as one request. Python: growth.results[0].growth. JS: growth.results[0].growth.

get_live

hot = client.get_live(limit=10)

Python: hot.data. JS: hot.data. Optional offset= and category= (Amazon Best Sellers by Category, Top Websites only).

Async

import asyncio
from trendsapi_wikipedia import AsyncTrendsAPI

async def main():
    c = AsyncTrendsAPI()
    return await asyncio.gather(
        c.get_time_series("large language model"),
        c.get_time_series("large language model", source="google search"),
    )

asyncio.run(main())

Shortened. The full README is on GitHub.

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

Wikipedia Trends API: common questions

Is Wikipedia Trends API MCP server safe?
Mostly: it is graded B (84/100). Read the Wikipedia Trends API safety report
How do I install Wikipedia Trends API?
It runs remotely at wikipedia.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 Wikipedia Trends API need an API key?
Yes. The registry entry asks for Authorization.
Is Wikipedia Trends API maintained?
The last commit was 78 days ago (2026-08-18). The latest release is v1.0.2.
Is Wikipedia Trends API up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Wikipedia Trends API 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 trendsapi.ai →