wikipedia-mcp-server

endpoint

https://wikipedia.caseyjhand.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is wikipedia-mcp-server live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is wikipedia-mcp-server free to use?

Yes — the hub reached it with no key and no payment.

What tools does wikipedia-mcp-server have?

6 tools: wikipedia_get_sections, wikipedia_get_summary, wikipedia_search_nearby, wikipedia_get_article, wikipedia_get_languages, wikipedia_search_articles.

Is wikipedia-mcp-server safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• wikipedia_get_sections reads unknown 4h ago

  Fetch the table of contents for a Wikipedia article. Returns section titles, heading levels, section numbering (e.g. "2.1"), and section_index values. The first entry is the lead section, index 0, titled Introduction — the text above the first heading, which Wikipedia's own table of contents omits. Pass a section_index to wikipedia_get_article to retrieve just that section. Useful for enumerating article structure before doing a targeted section read. Redirect pages are followed automatically.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "title"
    ],
    "properties": {
      "title": {
        "type": "string",
        "description": "Article title (e.g. \"Python (programming language)\"). A trailing #fragment is accepted and ignored; the characters < > [ ] { } and | cannot appear in a Wikipedia page name."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "Wikipedia language edition code (default \"en\"). Examples: \"fr\", \"de\", \"ja\"."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• wikipedia_get_summary reads unknown 11h ago

  Fetch the short article summary that answers "what is X?". The extract is a truncated fragment from the start of the lead section — usually a sentence or two, and as little as a tenth of the lead — alongside the Wikidata QID (wikibase_item) for cross-referencing with wikidata-mcp-server, a short description, a thumbnail URL, the canonical article URL, the revision the extract was read from, and, for a geotagged article, latitude and longitude that pass straight to wikipedia_search_nearby to answer "what else is notable near this". For the lead section in full, call wikipedia_get_article with section_index 0. Redirect pages are followed automatically. When page_type is "disambiguation", the title matched a disambiguation page — call wikipedia_search_articles with a more specific query to find the intended article. Prefer this over wikipedia_get_article unless article depth is needed.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "title"
    ],
    "properties": {
      "title": {
        "type": "string",
        "description": "Article title (URL-decoded), e.g. \"Python (programming language)\". A trailing #fragment is accepted and ignored; the characters < > [ ] { } and | cannot appear in a Wikipedia page name."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "Wikipedia language edition code (default \"en\"). Examples: \"fr\", \"de\", \"ja\"."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• wikipedia_search_nearby reads unknown 11h ago

  Find Wikipedia articles about places near a geographic coordinate. Returns articles sorted by distance from the query point, with titles, short descriptions, Wikidata QIDs, page IDs, coordinates, and distance in meters. Useful for "what is notable near X?" research workflows. Only articles carrying their own coordinate tag (GeoData, set on the article itself — not the Wikidata item's coordinate) are returned, and that tag is what places and measures each result; not all articles about locations are geotagged, and an article whose tag is wrong appears where the tag puts it, which its description usually makes plain.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "latitude",
      "longitude"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 500,
        "minimum": 1,
        "description": "Maximum number of results to return (default 10, max 500 — the MediaWiki geosearch ceiling). Must be a positive integer. Geosearch has no pagination, so articles past this limit are only reachable by raising it or searching narrower radii."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "Wikipedia language edition code (default \"en\"). Examples: \"fr\", \"de\", \"ja\"."
      },
      "latitude": {
        "type": "number",
        "description": "WGS 84 latitude in decimal degrees (range: −90 to 90)."
      },
      "longitude": {
        "type": "number",
        "description": "WGS 84 longitude in decimal degrees (range: −180 to 180)."
      },
      "radius_meters": {
        "type": "integer",
        "default": 1000,
        "maximum": 9007199254740991,
        "minimum": 10,
        "description": "Search radius in meters (default 1000, min 10, max 10000 — the MediaWiki geosearch bounds). Must be an integer; a value above the maximum is clamped to it."
      }
    },
    "additionalProperties": false
  }

  arguments 38 lines copy
• wikipedia_get_article reads unknown 4h ago

  Fetch article content as clean plain text. Without section_index: returns the full article with == Section == markers preserved for structure — or, when the article exceeds the size budget, a compact section outline (truncated: true) that points to wikipedia_get_sections plus a section_index read instead of the full text. With section_index (from wikipedia_get_sections): returns that section and every subsection nested under it, each heading above its own body. section_index 0 is the lead section, the text above the first heading, which is the full prose wikipedia_get_summary returns only a truncated fragment of. Section-targeted reads are faster and smaller when only part of the article is needed. Both paths keep superscripts and subscripts apart from the text beside them (10²³, H₂O), render formulas as their TeX, and render code samples as fenced blocks with their indentation intact. A section read also renders data tables as pipe-delimited rows (header row first) and infoboxes as "label: value" lines; a table too large to include leaves a "[table omitted: N rows]" marker in its place. The full-article path carries no data tables or infoboxes, so read the section for those. Tables used only for layout, such as multi-column lists, keep their content as ordinary text. Page furniture is omitted as well — maintenance banners, sister-project and library-resource boxes, portal bars, and spoken-article notices — while a hatnote naming a related article is kept. Every read returns the canonical article URL and the ID of the revision it was read from, for citation; a full read also returns that revision's timestamp. Redirect pages are followed automatically, and the citation fields name the target article.

  mcp-tool

  12345678910111213141516171819202122232425

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "title"
    ],
    "properties": {
      "title": {
        "type": "string",
        "description": "Article title (e.g. \"Python (programming language)\"). A trailing #fragment is accepted and ignored; the characters < > [ ] { } and | cannot appear in a Wikipedia page name."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "Wikipedia language edition code (default \"en\"). Examples: \"fr\", \"de\", \"ja\"."
      },
      "section_index": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 0,
        "description": "Section index from wikipedia_get_sections. 0 reads the lead section (Introduction) — the text above the first heading. Omit for the full article. Providing this returns the targeted section plus every subsection nested under it, as plain text."
      }
    },
    "additionalProperties": false
  }

  arguments 25 lines copy
• wikipedia_get_languages reads unknown 4h ago

  List the language editions available for a Wikipedia article. Returns language codes, article titles in each language, and full URLs. Useful for cross-language research and for discovering the correct article title in a target language before fetching it. A popular article exists in hundreds of editions, so pass editions to narrow the answer to the codes you care about — the codes with no article come back under missing, and total_languages still reports the full count. Redirect pages are followed automatically, and source_title reports the resolved article the links belong to. The language parameter specifies which edition to query from.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "title"
    ],
    "properties": {
      "title": {
        "type": "string",
        "description": "Article title in the source language edition. A trailing #fragment is accepted and ignored; the characters < > [ ] { } and | cannot appear in a Wikipedia page name."
      },
      "editions": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "minItems": 1,
        "description": "Edition codes to keep, e.g. [\"fr\", \"de\", \"gsw\"]. Each is matched case-insensitively against both edition_code and language_code, so either spelling of a mismatch edition finds it (\"gsw\" matches the edition whose edition_code is \"als\"). Omit to list every edition. A code with no article for this title is reported under missing rather than dropped, and is not a failure."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "Wikipedia language edition to query from (default \"en\"). Examples: \"fr\", \"de\", \"ja\"."
      }
    },
    "additionalProperties": false
  }

  arguments 27 lines copy
• wikipedia_search_articles reads unknown 11h ago

  Search Wikipedia articles by full-text query. Returns ranked results with plain-text titles, short descriptions, Wikidata QIDs, snippets (HTML stripped), page IDs, and word counts — the description is usually enough to tell same-named articles apart without a summary call per result. When Wikipedia has a spelling correction for the query, it is returned as suggestion. Best when the exact article title is unknown or when multiple articles on a topic are needed. Pass a result title to wikipedia_get_summary, wikipedia_get_article, or wikipedia_get_sections for follow-up reads. Use offset to page beyond the first result page. Supports all Wikipedia language editions.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233

  {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 50,
        "minimum": 1,
        "description": "Maximum number of results to return per page (default 10, max 50). Must be a positive integer."
      },
      "query": {
        "type": "string",
        "description": "Search query (e.g. \"Python programming language\"). Must not be empty."
      },
      "offset": {
        "type": "integer",
        "default": 0,
        "maximum": 9007199254740991,
        "minimum": 0,
        "description": "Result offset for pagination (default 0). Pass the nextOffset from a previous response to fetch the next page; limit still governs the per-page size. An offset past the total match count returns an empty result array, not an error. Wikipedia serves no result past 10,000, so an offset at or beyond that fails — narrow the query instead."
      },
      "language": {
        "type": "string",
        "default": "en",
        "description": "Wikipedia language edition code (default \"en\"). Examples: \"fr\", \"de\", \"ja\"."
      }
    },
    "additionalProperties": false
  }

  arguments 33 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• brapi.caseyjhand.com brapi-mcp-server mcp · 22 tools
• usaspending.caseyjhand.com usaspending-mcp-server mcp · 18 tools
• onebusaway.caseyjhand.com onebusaway-mcp-server mcp · 16 tools
• secedgar.caseyjhand.com secedgar-mcp-server mcp · 16 tools
• courtlistener.caseyjhand.com courtlistener-mcp-server mcp · 14 tools
• openfda.caseyjhand.com openfda-mcp-server mcp · 14 tools
• gbif-biodiversity.caseyjhand.com gbif-biodiversity-mcp-server mcp · 13 tools
• openfec.caseyjhand.com openfec-mcp-server mcp · 12 tools

101 more sit on this domain. All of them.