Wikipedia Trends API MCP Server

by trendsapi Your server? Claim it

answering

Wikipedia Trends API is answering right now. Last checked 15 min ago. It exposes 4 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 50 days of history · worst day 99%

50 days agonow

100.0%

Uptime 24h

90 of 90 checks

Tools

read from the server

425 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 August 2026. No other catalogue keeps this.

20 Sep 4 tool descriptions were rewritten trends___get_growth, trends___get_time_series, trends___get_top_posts and 1 more

16 Sep a tool appeared trends___get_top_posts

5 Sep a tool description was rewritten trends___get_top_trends

5 Sep a tool changed the parameters it asks for trends___get_top_trends

29 Aug a tool description was rewritten trends___get_top_trends

29 Aug a tool changed the parameters it asks for trends___get_top_trends

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "wikipedia": {
      "url": "https://wikipedia.api.trendsapi.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.wikipedia]
url = "https://wikipedia.api.trendsapi.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wikipedia": {
      "url": "https://wikipedia.api.trendsapi.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "wikipedia": {
      "url": "https://wikipedia.api.trendsapi.ai/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trends

trends___get_growth

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_series

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_posts

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_trends

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.

Endpoints

URL	Transport	State	Latency	Checked
https://wikipedia.api.trendsapi.ai/mcp	streamable-http	answering	347 ms	15 min ago

Alternatives to Wikipedia Trends API

same job, measured the same way

Wikipedia Trends MCP

by trendsmcp

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

4 tools answering

Wikipedia Pageviews MCP

by mrfentmen

Wikipedia page view statistics. No key required.

local only

wikiviews

by pipeworx-io

Wikiviews MCP — wraps the Wikimedia Pageviews API (free, no auth)

38 tools answering

wikipedia

by pipeworx-io

Wikipedia MCP — wraps Wikipedia REST API (free, no auth)

36 tools answering

On This Day MCP

by mrfentmen

Historic births, deaths, and events for any date from Wikipedia. No key required.

local only

Wikitrending MCP

by mrfentmen

Wikipedia featured content for a day. No key required.

local only

wikifeed

by pipeworx-io

Wikifeed MCP — wraps Wikimedia Feed API (free, no auth)

39 tools answering

Academic Research MCP Server

by thenextgennexus

Search arXiv, Google Scholar, and Wikipedia for academic papers and knowledge

25 installs/wk local only

Wikipedia Trends API — questions

Answers built from our own checks of this server.

What can Wikipedia Trends API do?

It exposes 4 tools, read directly from the server on our last check. Among them: trends___get_growth, trends___get_time_series, trends___get_top_posts, trends___get_top_trends. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Wikipedia Trends API working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 425 ms. The bar chart above shows every period we have measured.

Is Wikipedia Trends API still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Wikipedia Trends API?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Wikipedia Trends API need an API key?

No. Wikipedia Trends API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Wikipedia Trends API?

It answers our handshake in 425 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.