Websharp
概览
作者提供的说明(英文原文)
Search the web and extract article text for LLMs.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: Streamable HTTP
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- Docker已安装 Docker
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"websharp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/jessegador/websharp-mcp:v0.99.0-rc2"
]
}
}
}在终端中运行这条命令
claude mcp add websharp -- docker run -i --rm docker.io/jessegador/websharp-mcp:v0.99.0-rc2或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"websharp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/jessegador/websharp-mcp:v0.99.0-rc2"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"websharp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/jessegador/websharp-mcp:v0.99.0-rc2"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 jgador 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5686 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5686 个服务器的 0% 更新
- 基础检查结果等于或优于此分类中其他 5686 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Websharp 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(v0.99.0-rc2)于14个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
WebSharp MCP HTTP Server
WebSharp is a Model Context Protocol (MCP) server written in C# (.NET 9) that exposes web search and readable page extraction tools over the streamable HTTP transport. It pairs a SearXNG metasearch instance with the SmartReader content extraction library and ships with Docker assets so you can run everything locally with one command.
Highlights
- Streamable HTTP MCP endpoint served by ASP.NET Core via
ModelContextProtocol.AspNetCore. - SearXNG-backed metasearch tool that returns both a readable summary and structured JSON metadata.
- SmartReader-powered page reader tools for single URLs or batches, ideal for grounding and fact checking workflows.
- Container-first development story with Docker Compose and an inspector-ready
.mcp.jsonprofile.
Available MCP tools
web_search
| Parameter | Type | Default | Notes |
|---|---|---|---|
query | string | _required_ | Free-form search string submitted to the configured search backend (defaults to SearXNG). |
limit | integer | 10 | Maximum number of results to surface in the text summary. When set to 0 or negative, the parameter is omitted and the backend decides the result count. |
categories | string | "general" | Comma-separated categories forwarded to the backend (for SearXNG, examples include general,it,science). |
language | string | "en" | Language tag forwarded to the backend. When using the default SearXNG instance, see its language list. |
Response
- Text summary showing the top results, related suggestions, and any unresponsive engines.
structuredContentcontains a JSON object with:query: echo of the evaluated query string.items: array of result objects (title,url,content,engine/engines,category,positions,parsed_url).suggestions: related queries returned by the backend (SearXNG surfaces them when available).unresponsive_engines: list of engines that timed out or failed, with optional messages.error: present when the search could not be completed.
web_page_read
| Parameter | Type | Default | Notes |
|---|---|---|---|
urls | array | _required_ | One or more absolute HTTP/HTTPS URLs to fetch and parse. |
Response
- When a single URL is provided, returns the article title, excerpt, a preview of the readable text (~800 characters), and footer metadata (source URL, detected language).
- When multiple URLs are provided, the summary includes overall success/failure counts, per-page details (title, URL, full text, language), and error messages for any failures. Requests run concurrently and honor the MCP cancellation token.
structuredContentis not populated; all data is returned in the text block.
Run everything with Docker Compose
- Install Docker Desktop (or another OCI-compatible runtime) and ensure it is running.
- From the repository root, start both the SearXNG dependency and the MCP server:
docker compose -f docker-compose.yaml --project-name websharp up -d(add--buildon the first run or whenever the Dockerfile changes). - Wait until the
websharp-mcpcontainer reportsNow listening on: http://0.0.0.0:8080. - The MCP server is now reachable at
http://localhost:8081(mapped from container port 8080). SearXNG is available athttp://localhost:8080/for inspection.
Build the Docker image manually
Run the server image build without Docker Compose from the repository root:
docker build -f .\src\WebSharp.Mcp.Http\Dockerfile -t jessegador/websharp-mcp:v0.99.0-rc2 --no-cache src
Update -t to match the image registry and tag you plan to publish.
Connect with the MCP Inspector
- Start (or keep running) the compose stack above.
- Launch the Inspector with the included client profile:
npx -y @modelcontextprotocol/inspector --config .\.mcp.json --server websharp-mcp - Copy the printed token into the Inspector UI by opening
http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=in your browser. - In the Inspector UI, pick the
websharp-mcpserver to explore the available tools and try calls right away.
Running from source
- Install the .NET 9 SDK.
- Ensure you have access to a SearXNG endpoint. The easiest option is to keep using the Docker Compose service and export
Searxng__BaseUrltohttp://localhost:8080before starting the app. - Launch the server:
dotnet run --project src/WebSharp.Mcp.Http/WebSharp.Mcp.Http.csproj --urls http://localhost:8081 - The MCP endpoint listens on
/. InDEBUGbuilds you can hit/__routesto inspect the configured ASP.NET endpoints.
Configuration
| Environment variable | Default | Description |
|---|---|---|
ASPNETCORE_URLS | http://0.0.0.0:8080 (Docker) | Listening address(es) for the HTTP server. Override to change the exposed MCP port. |
Searxng__BaseUrl | http://searxng:8080 | Base URL of the SearXNG instance. Required if you are not running the bundled Docker service. Must be an absolute URI. |
Cors__AllowAnyOrigin | true | Permit all origins. Set to false when you want to limit callers via Cors__AllowedOrigins__0= style keys. |
Cors__AllowAnyHeader | true | Allow all request headers. |
Cors__AllowAnyMethod | true | Allow all HTTP methods. |
Cors__AllowCredentials | false | When true, credentials are accepted and you must explicitly enumerate origins. |
Cors__AllowedOrigins__{n} | _(empty)_ | Optional origin allowlist entries when AllowAnyOrigin is false. |
Cors__AllowedHeaders__{n} | _(empty)_ | Optional header allowlist. |
Cors__AllowedMethods__{n} | _(empty)_ | Optional method allowlist. |
All configuration values can also be supplied via appsettings.json/appsettings.Development.json. The Docker Compose definition mounts the correct defaults for local experimentation.
Using a different SearXNG instance
- Point
Searxng__BaseUrlat your hosted SearXNG deployment (for examplehttps://searxng.example.com). - Make sure the endpoint you target exposes the SearXNG Search API and permits the categories/languages you request.
- Consider adjusting the bundled
searxng/settings.ymlto tune activated engines, safe search, or rate limits before publishing to the MCP registry.
Security notes
- The HTTP transport does not include authentication. Run behind a reverse proxy, tunnel, or VPN when exposing beyond localhost.
- CORS defaults to permissive settings for debugging. Tighten them before deploying to shared environments.
- The server respects MCP cancellation tokens, and page fetches enforce short HTTP timeouts to avoid hanging client sessions.
Registry metadata
- Name:
websharp-mcp - Transport:
streamable-http - Endpoint:
/ - See
.mcp.jsonfor a ready-to-use inspector profile.
License
This project is available under the MIT license (see LICENSE).