How do I install Web?

Web is a remote plugin. You do not need to install anything locally. Add the server URL to your AI app's MCP configuration and you are ready to go.

Yes. Web passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What AI apps work with Web?

Web uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Web MCP Server

by Kamatanuj

Developer ToolsLow Risk10.0MCP RegistryRemote

Free

Server data from the Official MCP Registry

WebMCP demo store: same catalog via MCP tool calls vs DOM scraping. -79% bytes, -42% tokens.

About

WebMCP demo store: same catalog via MCP tool calls vs DOM scraping. -79% bytes, -42% tokens.

Remote endpoints: streamable-http: https://demowithmcp.converso.work/mcp

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

5 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

env_vars

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

Shell Command Execution

Runs commands on the server that hosts it, not on your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-kamatanuj-webmcp-store": {
      "url": "https://demowithmcp.converso.work/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

WebMCP Demo Store — one-file server, two modes, one benchmark

Same store, same tools, two delivery modes:

WebMCP mode — the page exposes its catalog through MCP tool calls (MCP-over-HTTP /mcp, plus Chrome-native document.modelContext), so an agent reads only what the task needs.
Plain mode — the same store as an ordinary website; the agent parses full HTML pages, as every agent must today.

Benchmark (150-product catalog, identical tasks): 79% less action bytes, 42% fewer input tokens, 8/8 tasks correct in both modes. DOM mode wins on small catalogs then collapses; WebMCP wins with age. Crossover report: report.html → WebMCP_Comparison_Report.pdf.

Run it

python3 server.py                    # plain mode      → http://localhost:9501
MCP=1 PORT=9502 python3 server.py    # WebMCP mode     → http://localhost:9502 + /mcp

stdlib-only (http.server, json, uuid, threading) — no pip install, no dependencies.

Live demos

plain: https://demonomcp.converso.work
WebMCP: https://demowithmcp.converso.work (.well-known/mcp discovery, /mcp endpoint)
launch package (deck, whitepaper, reports): https://demowithmcp.converso.work/launch.html

Chrome-native WebMCP test (13 Oct 2026)

Chrome 154 + --enable-features=WebMCP exposes document.modelContext on HTTPS origins (about:blank excluded).

Registered the 5-tool store contract via the IMPERATIVE API (registerTool): search_products, add_to_cart, get_cart, checkout (server-backed; all fetches in-page).
Standard client flow verified: getTools() discovery → executeTool() calls → orders 1017/1018 placed, T2/T4/T8 picks correct (HP Pavilion 14, Razer DeathAdder, OnePlus 12R).
154 build quirks found & worked around:
1. executeTool(tool, args) requires args as a JSON string (object form throws "Failed to parse input arguments"); return values are JSON strings too — JSON.parse both sides.
2. Tools can't be re-registered under the same name (InvalidStateError) — reload the page to reset.
3. Flag/feature name: --enable-features=WebMCP works headless; docs' chrome://flags/#enable-webmcp-testing is the manual path. Note: API is document.modelContext (moved from navigator since July 2026 build).
Takeaway: the demo's tool contract is compatible with Chrome's native WebMCP, not just our JSON-RPC shim. When Chrome ships the client agent (Gemini-in-Chrome), the store is already agent-ready.

Repo layout

path	what
`server.py`	the whole thing: store + cart + orders + MCP transport (`MCP=1`) + static/report serving
`catalog.json` / `catalog_10.json`	150-product / 10-product demo catalogs
`compare.py`, `compare_llm.py`, `browser_llm.py`	benchmark harnesses (DOM-mode agent, LLM-token accounting, browser-native flow)
`make_report.py`	regenerates the HTML/PDF reports from `results.json` / `agg_150_vs_30.json`
`whitepaper.html`, `report.html`, `.pdf`, `chart_*.png`	strategy + evidence artifacts (launch deck included)
`weekly_recap.py`	counters + live-URL digest (used by the ops cron)

License

MIT.

Reviews

No reviews yet

Be the first to review this server!

4.7

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.