Skip to content
External endpointresponds

mcp-server

MCP server for WindowsForum.com with search, document retrieval, and real-time forum analytics.

Endpoint URL
https://mcp.windowsforum.com
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
172 ms
Response record
4 of 4 rounds
Transport
sse
Source
mcp_registry
Registry name
com.windowsforum/mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Universal MCP Server
Version
3.4.7
Capability keys
experimental, logging, prompts, resources, tools, tasks, extensions
Tool names
search, fetch, search_semantic, search_threads, get_time, get_kb_article, search_kb, get_thread_posts, search_mysql, search_elastic, get_thread, list_threads, get_post, get_user, get_forum, get_forum_updates, get_online_users, get_latest_registered_users, get_forum_statistics, search_posts, search_users, get_windows_news_posts
Instructions excerpt

This MCP server provides comprehensive search and document retrieval capabilities for WindowsForum.com data and Microsoft Knowledge Base articles. It's designed to work with ChatGPT's chat, agent mode, and deep research features. Available capabilities: - Search WindowsForum threads and posts via BM25 (Elasticsearch) and semantic vector search - Fetch complete documents with citations - Access user, thread, and forum information - Get real-time updates and analytics - Look up Microsoft KB articles directly from support.microsoft.com Use the search tool with source="auto" (default) for best results — it combines keyword (BM25) and semantic (vector) search. Use source="semantic" for pure vector similarity search, or source="windowsforum" for keyword-only search. Then use the fetch tool to retrieve complete document content with citations. When a user asks about a specific KB number (e.g. "KB5044284"), use the get_kb_article tool to fetch the official Microsoft article directly. Use

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 177ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 339ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 145ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 172ms
Back to MCP directory