Wikipedia Trends MCP Server

by trendsmcp Your server? Claim it

answering

Wikipedia Trends MCP is answering right now. Last checked 14 min ago. It exposes 4 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 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

494 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 5

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

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 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

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

{
  "mcpServers": {
    "wikipedia": {
      "url": "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

{
  "mcpServers": {
    "wikipedia": {
      "url": "https://wikipedia.api.trendsmcp.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. Prefer this over get_time_series for growth questions. 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. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

trends___get_time_series

Full historical series for one keyword and one source (0-100 values, plus volume when available). Use for charting or custom math. Not for live 'what's trending now' boards (use get_top_trends). For most growth questions, use get_growth. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

trends___get_top_posts

Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. Use when the user already has a hashtag and wants the posts winning on it. For ranking hashtags themselves, use get_top_trends. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

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', always pass category. 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 handler fetches that one board live. App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. For an app's history use get_growth or get_time_series with source app downloads or app rankings and an Android bundle ID. Do not use get_time_series for live boards. If the request is rate limited or the monthly quota is used up, tell the user their plan limit is reached.

Endpoints

URL	Transport	State	Latency	Checked
https://wikipedia.api.trendsmcp.ai/mcp	streamable-http	answering	521 ms	14 min ago

Alternatives to Wikipedia Trends MCP

same job, measured the same way

Wikipedia Trends API

by trendsapi

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

4 tools answering

wikiviews

by pipeworx-io

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

38 tools answering

LLM Wiki MCP

by flsteven87

MCP server for Karpathy-style LLM wikis: persistent markdown your agent grows over time.

66 installs/wk local only

Pmwiki MCP

by kcofoni

MCP server for searching and reading PmWiki pages with text queries and group filtering.

local only

wikipedia

by pipeworx-io

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

36 tools answering

Trends MCP

by trendsmcp

Trend data from Google Trends, YouTube, TikTok, Reddit, Amazon, Wikipedia, npm, Steam and more

4 tools answering

Ariel Memory

by cipher208

Two-layer memory MCP server for AI agents with 37 tools, RAG, graphs, wiki, auth

40 installs/wk local only

Redmine MCP Server

by igorolv

Redmine for AI agents: issues, projects, wiki, attachments, time entries and release analytics

local only

Wikipedia Trends MCP — questions

Answers built from our own checks of this server.

What can Wikipedia Trends MCP 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 MCP 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 494 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 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 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 4 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 494 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.