Is io.github.jgador/websharp safe to use?

io.github.jgador/websharp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.jgador/websharp?

io.github.jgador/websharp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.jgador/websharp?

io.github.jgador/websharp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.jgador/websharp actively maintained?

io.github.jgador/websharp is less actively maintained — last commit was 248 days ago. It has 1 GitHub stars.

io.github.jgador/websharp

@modelcontextprotocol/inspector

Search the web and extract article text for LLMs.

1 191.2k/wk 0 tools GitHub npm

No known CVEs

No license

Stale

Last commit 248d ago

Works with most clients

Transport: stdio, sse, http

0 tools

Grade F

Edit this pageView history

Search Browser

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

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

{
  "mcpServers": {
    "io-github-jgador-websharp": {
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-jgador-websharp)](https://mcppedia.org/s/io-github-jgador-websharp)

Read me

What io.github.jgador/websharp does

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.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@modelcontextprotocol/inspector' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

50/100across 5 weighted dimensions

How we score →

0255075100

−50

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

2 fixed

CVE-2025-58444medium · fixedCVSS 4

MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server

An XSS flaw exists in the MCP Inspector local development tool when it renders a redirect URL returned by a remote MCP server. If the Inspector connects to an untrusted server, a crafted redirect can inject script into the Inspector context and, via the built-in proxy, be leveraged to trigger arbitrary command execution on the developer machine. Version 0.16.6 hardens URL handling/validation and prevents script execution. > Thank you to the following researchers for their reports and contributi

Affected: >= 0Fixed in 0.16.6source →

CVE-2025-49596medium · fixedCVSS 4

MCP Inspector proxy server lacks authentication between the Inspector client and proxy

Versions of MCP Inspector below 0.14.1 are vulnerable to remote code execution due to lack of authentication between the Inspector client and proxy, allowing unauthenticated requests to launch MCP commands over stdio. Users should immediately upgrade to version 0.14.1 or later to address these vulnerabilities. Credit: Rémy Marot <bughunters@tenable.com>

Affected: >= 0Fixed in 0.14.1source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.jgador/websharp safe to use?: io.github.jgador/websharp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.jgador/websharp?: io.github.jgador/websharp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.jgador/websharp?: io.github.jgador/websharp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.jgador/websharp actively maintained?: io.github.jgador/websharp is less actively maintained — last commit was 248 days ago. It has 1 GitHub stars.

Similar servers

Others in search / browser

View all →

Brave Search MCP Server98

Web and local search using Brave Search API

86.4k 2

Tavily Mcp96

Production ready MCP server with real-time search, extract, map & crawl.

2.0k 4

Puppeteer MCP Server95

Browser automation with Puppeteer for web scraping and testing

86.5k 5

Qmd95

mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local

25.8k 4

MCP Security Weekly

Get CVE alerts and security updates for io.github.jgador/websharp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Search Browser

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

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

{
  "mcpServers": {
    "io-github-jgador-websharp": {
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-jgador-websharp)](https://mcppedia.org/s/io-github-jgador-websharp)

Read me

What io.github.jgador/websharp does

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@modelcontextprotocol/inspector' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

WebSharp MCP HTTP Server

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.json profile.

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.
structuredContent contains 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.
structuredContent is 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 --build on the first run or whenever the Dockerfile changes).
Wait until the websharp-mcp container reports Now 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 at http://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/?MC

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

50/100across 5 weighted dimensions

How we score →

0255075100

−50

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

2 fixed

CVE-2025-58444medium · fixedCVSS 4

MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server

Affected: >= 0Fixed in 0.16.6source →

CVE-2025-49596medium · fixedCVSS 4

MCP Inspector proxy server lacks authentication between the Inspector client and proxy

Affected: >= 0Fixed in 0.14.1source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.jgador/websharp safe to use?: io.github.jgador/websharp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.jgador/websharp?: io.github.jgador/websharp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.jgador/websharp?: io.github.jgador/websharp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.jgador/websharp actively maintained?: io.github.jgador/websharp is less actively maintained — last commit was 248 days ago. It has 1 GitHub stars.