Wikipedia MCP — wraps Wikipedia REST API (free, no auth)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 36 tools
Most tools target distinct resources, but the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research cluster is heavily overlapping—beta is even documented as currently identical to the stable router—and the six Polymarket tools plus discover_tools/suggest_questions/pipeworx_trending blur into each other. Descriptions do invest effort in steering ('prefer X over Y'), which keeps it navigable but not clean.
Overwhelmingly snake_case and readable, but the set mixes verb-first (get_article_extract, search_wikipedia, validate_claim, resolve_entity) with noun-first conventions (entity_profile, recent_changes, recent_alerts, ai_visibility_check). No camelCase or chaos, just a mild inconsistency in leading token.
36 tools is heavy for a single server surface and includes clearly redundant members (the beta router variant, multiple near-duplicate discovery tools). As an aggregator gateway some breadth is justified, but the count exceeds the point where each tool clearly earns its place.
Lifecycle coverage is strong where it exists—memory (remember/recall/forget) and subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts) are complete, and Wikipedia reads span summary/sections/extract/search. Gaps are minor, though the surface is sprawling enough that it is hard to argue full coverage of any one domain.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."resolve_entity1 field changedInput schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."Wikifeed MCP — wraps Wikimedia Feed API (free, no auth)
Wikidata MCP — wraps Wikidata API (wikidata.org/w/api.php)
Wikiviews MCP — wraps the Wikimedia Pageviews API (free, no auth)
Add one secure layer between your agents and this server.