Compatible with every major AI agent and IDE
What is the HTML XSS Sanitizer MCP Server?
If you ask an AI to 'clean this HTML before saving it', it will likely fail to catch obfuscated XSS vectors hidden in Base64 or obscure event handlers. LLMs do not have native rendering engines to test payloads. This MCP provides an enterprise-grade security shield for agents that handle public inputs.
The Superpowers
- Surgical Cleaning: Uses
sanitize-htmlto strip dangerous tags (,) and maliciousonloadevents. - Zero-Trust Input: Enforces a strict whitelist of safe tags, ensuring that what goes into your database cannot execute harmful code in a browser.
Built-in capabilities (1)
Pass the raw HTML and receive clean, safe HTML with dangerous tags and attributes stripped. Strips malicious XSS vectors and unsafe tags from HTML payloads before they are saved to a database
Why VS Code Copilot?
GitHub Copilot Agent mode brings HTML XSS Sanitizer data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 1 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
HTML XSS Sanitizer in VS Code Copilot
HTML XSS Sanitizer and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect HTML XSS Sanitizer to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for HTML XSS Sanitizer in VS Code Copilot
The HTML XSS Sanitizer MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
HTML XSS Sanitizer for VS Code Copilot
Every tool call from VS Code Copilot to the HTML XSS Sanitizer MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Does it remove CSS?
By default, it removes unsafe styles but leaves the structure intact.
Is it better than asking the LLM to do it?
Absolutely. LLMs are easily bypassed by obfuscated XSS payloads. This engine relies on strict deterministic whitelisting.
Are images allowed?
Yes, <img> tags are whitelisted, but only with safe attributes like src and alt.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Mercury
10 toolsEquip your AI agent with direct access to Mercury — check account balances, review transactions, and manage recipients without opening the banking dashboard.

Kontak
10 toolsManage communications — list messages, send SMS, and audit contacts.

ShipEngine
12 toolsCompare shipping rates, print labels, and track packages across UPS, FedEx, USPS, and dozens of global carriers instantly.

Pipedream
7 toolsManage Pipedream serverless workflows, sources, webhooks, and raw event data natively via AI agents.
