Wikipedia Trends API MCP Server

by trendsapi Your server? Claim it

answering

Wikipedia Trends API is answering right now. Last checked 9 min ago. It exposes 6 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 91 days of history · worst day 99%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

491 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 35

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

6 Nov 4 tool descriptions were rewritten trends___get_context, trends___get_growth, trends___get_time_series and 1 more

6 Nov 4 tools changed the parameters they ask for trends___get_context, trends___get_growth, trends___get_time_series and 1 more

6 Nov a tool appeared trends___get_reviews

6 Nov a tool disappeared trends___get_top_posts

31 Oct 3 tools changed the parameters they ask for4 times that day trends___get_growth, trends___get_time_series, trends___get_top_trends

31 Oct a tool description was rewritten trends___get_top_trends

26 Oct 3 tools changed the parameters they ask for5 times that day trends___get_growth, trends___get_time_series, trends___get_top_posts

26 Oct a tool appeared trends___get_context

25 Oct 3 tools changed the parameters they ask for trends___get_growth, trends___get_time_series, trends___get_top_trends

25 Oct a tool description was rewritten trends___get_usage

and 13 more, back to 29 August 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "wikipedia": {
      "type": "http",
      "url": "https://wikipedia.api.trendsapi.ai/mcp"
    }
  }
}

Available tools 6

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_context

What people are posting, reading and betting about a keyword right now, or with hashtag=true the top TikTok and Instagram posts on one hashtag. 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 data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

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. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

trends___get_reviews

What customers say about a brand, app, product or place. Returns, per source, the matched listing with its all-time rating and review count, the newest reviews (stars, text, the company's reply) and a summary (average stars, star counts, share negative, share replied). Use it for brand sentiment and complaints; get_context covers social posts. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. 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 on one or more sources (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. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. 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 boards: one feed type, several, or 'all'. 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. Costs 1 request per data type (source or board) in the call; boards cost 1 request per 10 rows. Only data types that answer are charged; the answer says requests_charged. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

trends___get_usage

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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

trends___get_top_posts

removed 7 Nov 2026

Endpoints

URL	Transport	State	Latency	Checked
https://wikipedia.api.trendsapi.ai/mcp	streamable-http	answering	407 ms	9 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

6 tools answering

Attention Trends

by workers-shopttyass-85f-attention-trends

Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid).

3 tools answering

Wikipedia Pageviews MCP

by mrfentmen

Wikipedia page view statistics. No key required.

44 installs/wk local only

Wikiviews

by pipeworx-io

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

118 installs/wk 47 tools answering

Wikipedia

by pipeworx-io

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

134 installs/wk 49 tools answering

On This Day MCP

by mrfentmen

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

49 installs/wk local only

Faceabot Wikipedia

by faceabot

Search and read Wikipedia in any language: summaries and full articles. Free, no key.

3 tools answering

Bot Space

by bsp

Free, no-login forum, wiki and chat for AI bots: share hard-won fixes, peer validation, topic karma.

12 tools answering

Wikipedia Trends API — questions

Answers built from our own checks of this server.

What can Wikipedia Trends API do?

It exposes 6 tools, read directly from the server on our last check. Among them: trends___get_context, trends___get_growth, trends___get_reviews, trends___get_time_series, trends___get_top_trends, trends___get_usage. 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 91 of 91 checks got a reply (100.0%), average response time 491 ms. The bar chart above shows every period we have measured.

Did Wikipedia Trends API ever remove tools?

Yes. trends___get_top_posts is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

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 in the form 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 6 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 491 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.