HTML Entities Skill

Overview

HTML Entities Encoder/Decoder works by converting characters like <, >, &, quotes, and slashes into their HTML entity equivalents or decoding them back to original characters. Essential for XSS prevention.

Live Test HTML Entities Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as HTMLEntitiesSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "HTMLEntitiesSkill",
  "arguments": {
    "html": "<div>Hello & Welcome</div>"
  }
}

You do not name the tool yourself; the model picks it. Asking about <div>Hello & Welcome</div> in the terms this skill covers is enough for it to reach for HTMLEntitiesSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`html`Required	string	The HTML content to encode
`action`Optional	string	The action to perform `encodedecode` default encode

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "action": "encode",
    "original": "<div class=\"test\">Hello & World</div>",
    "encoded": "&lt;div class=&quot;test&quot;&gt;Hello &amp; World&lt;&#x2F;div&gt;",
    "entities_replaced": [
      "<",
      "\"",
      ">",
      "&",
      "/"
    ],
    "count": 8
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`action`	string	`encode`	The action performed on the HTML content
`original`	string	`<div class="test">Hello & World</div>`	The original HTML entities before decoding
`encoded`	string	`<div class="test">Hello & World</div>`	The HTML content with entities decoded
`entities_replaced`	array	`["<","\"",">"]`	Array of entity patterns that were replaced
`count`	number	`8`	Total number of entity replacements made

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

XSS Prevention: Encode user input before displaying in HTML to prevent cross-site scripting (XSS) attacks
Data Display: Decode HTML entities in stored content to display special characters correctly in web applications
Content Migration: Encode or decode HTML entities when migrating content between systems with different encoding requirements
API Integration: Properly encode HTML content before sending to APIs or decode entities received from external sources

Other ways to use HTML Entities Skill

Set up HTML Entities Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →