Wikipedia Trends MCP is answering right now. Last checked 4 min ago. It exposes 6 tools.
Wikipedia page views over time, with growth for any article topic. Free key at trendsmcp.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
92 of 92 checks
6
Tools
read from the server
476 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 25
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 August 2026. No other catalogue keeps this.
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
23 Oct
a tool appeared
trends___get_usage
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
and 6 more, back to 29 August 2026
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 4 min ago.
run in your terminal
claude mcp add wikipedia --transport http https://wikipedia.api.trendsmcp.ai/mcpSettings → Connectors → Add custom connector, then paste this address
https://wikipedia.api.trendsmcp.ai/mcp~/.codex/config.toml
[mcp_servers.wikipedia]
url = "https://wikipedia.api.trendsmcp.ai/mcp".cursor/mcp.json
{
"mcpServers": {
"wikipedia": {
"url": "https://wikipedia.api.trendsmcp.ai/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"wikipedia": {
"type": "http",
"url": "https://wikipedia.api.trendsmcp.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. 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_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', '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_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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://wikipedia.api.trendsmcp.ai/mcp | streamable-http | answering | 577 ms | 4 min ago |
Alternatives to Wikipedia Trends MCP
same job, measured the same wayWikipedia Trends API
by trendsapi
Wikipedia page view trends for any topic over time. Free key at trendsapi.ai
Attention Trends
by workers-shopttyass-85f-attention-trends
Topic popularity, interest over time and trending topics from Wikipedia pageviews (x402 paid).
Wikiviews
by pipeworx-io
Wikiviews MCP — wraps the Wikimedia Pageviews API (free, no auth)…
LLM Wiki MCP
by flsteven87
MCP server for Karpathy-style LLM wikis: persistent markdown your agent grows over time.
Faceabot Wikipedia
by faceabot
Search and read Wikipedia in any language: summaries and full articles. Free, no key.
Wikipedia Pageviews MCP
by mrfentmen
Wikipedia page view statistics. No key required.
Pmwiki MCP
by kcofoni
MCP server for searching and reading PmWiki pages with text queries and group filtering.
Wikipedia
by pipeworx-io
Wikipedia MCP — wraps Wikipedia REST API (free, no auth)
Wikipedia Trends MCP — questions
Answers built from our own checks of this server.
What can Wikipedia Trends MCP do?
It exposes 6 tools, read directly from the server on our last check. Among them: trends___get_context, trends___get_growth, trends___get_time_series, trends___get_top_posts, 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 MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 476 ms. The bar chart above shows every period we have measured.
Is Wikipedia Trends MCP 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 MCP?
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 MCP need an API key?
No. Wikipedia Trends MCP 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 MCP?
It answers our handshake in 476 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.