How do I install Sezzlee XML?

Install Sezzlee XML in your harness: MCP — git clone https://github.com/sezzlee/mcp. Full step-by-step guidance is on the HOL plugin page.

How do I install Sezzlee XML in MCP?

To install Sezzlee XML in MCP, start with git clone https://github.com/sezzlee/mcp. The complete step-by-step install guide for MCP is on the HOL plugin page.

Who publishes Sezzlee XML?

Sezzlee XML is published by io.github.sezzlee and listed on HOL.

Sezzlee XML

io.github.sezzlee/xml · v0.5.1 · MCP server

by io.github.sezzleeOfficial MCP registry · not scanned

Query local XML documents with XPath, paged and sandboxed to one folder. Read-only.

Install Source Claim this MCP server

Follow0

Trust ScoreNot scanned Security scanNot scanned Components1

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Sezzlee XML a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

1 MCP server

Before you install

Sign-in: Not declared
Declared access: Not declared
License: Not declared

Check before relying on it

HOL has not scanned this listing yet, so trust and security scores are unknown.
The publisher has not verified ownership on HOL.
No license declared in the manifest.

What is Sezzlee XML?

Sezzlee XML is a published mcp server plugin for AI coding agents in the MCP ecosystem, developed by io.github.sezzlee and distributed through the HOL AI plugin registry. Query local XML documents with XPath, paged and sandboxed to one folder. Read-only.

Canonical slug: io.github.sezzlee/xml
Version: v0.5.1 · updated Oct 11, 2026
Open data: entity.json (JSON-LD)

Registry snapshot

Repository: https://github.com/sezzlee/mcp
Homepage: https://docs.sezzlee.app/docs/xml-mcp/quickstart
Canonical profile: https://hol.org/registry/plugins/io.github.sezzlee%2Fxml
Owner verification: Not verified
Scanner: Registry pipeline
Security result: Not scanned
Digest verified: No

Trust and security

Provenance

Plugin root: .
Source repo: https://github.com/sezzlee/mcp
Source commit: Unpinned
Publisher verified: No
Owner verified: Not owner verified

Security posture

See how the Trust Score is computed

Not scanned

Security result

N/A

Security score

High findings

Published advisories

None matched in OSV, checked 2026-10-30. This covers published advisories only, not problems nobody has reported.

OSV is matched against the exact package versions this listing names.

Findings

No normalized findings were returned for this plugin.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs

Clone the repository

shell

2
Register the server in your MCP client
Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.
3
Verify the server
Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "source": "official-mcp-registry",
  "evidenceState": "unscanned_source",
  "registryName": "io.github.sezzlee/xml",
  "publishedAt": "2026-10-11T17:14:33.173905Z",
  "packages": [
    {
      "registryType": "npm",
      "identifier": "@sezzlee/xml-mcp",
      "version": "0.5.1",
      "transport": "stdio",
      "requiredEnvironment": []
    }
  ],
  "remotes": []
}

File inventory

File inventory is unavailable for this plugin right now.

Sezzlee XML — Frequently asked questions

What is Sezzlee XML?: Sezzlee XML is an AI plugin in the HOL registry. Query local XML documents with XPath, paged and sandboxed to one folder. Read-only.
How do I install Sezzlee XML?: Install Sezzlee XML in your harness: MCP — git clone https://github.com/sezzlee/mcp. Full step-by-step guidance is on the HOL plugin page.
How do I install Sezzlee XML in MCP?: To install Sezzlee XML in MCP, start with git clone https://github.com/sezzlee/mcp. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes Sezzlee XML?: Sezzlee XML is published by io.github.sezzlee and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Claude Code official marketplaceNot listed
Plugins Anthropic maintains or selected for the marketplace Claude Code ships with.
Claude community directoryNot listed
Plugins submitted through claude.ai that passed Anthropic’s review; the list is a nightly mirror.
Codex curated marketplaceNot listed
Plugins OpenAI lists in the marketplace Codex ships with.
Cursor official pluginsNot in public list
Plugins Cursor publishes itself. Cursor does not publish its list of third-party Marketplace plugins.
Awesome Codex Plugins (HOL)Not listed
The community Codex plugin list HOL maintains on GitHub.
Official MCP RegistryImported
HOL imported this listing from the registry.

Lists last read Oct 31, 2026. HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here: <5; HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports: <10; Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces: <5; Workspaces that approved it or include it in an approved-plugin feed, as of today.