Publisher · GitHub account
MCP servers published by Nizoka
2 servers in the official MCP Registry are published under the namespace io.github.Nizoka/ and have a page in this directory: both run locally from a package. First published 2026-09-07; latest update 2026-09-24.
What this publisher publishes
Names under io.github.Nizoka/ can only be published by someone who signs in to the MCP Registry as the GitHub user Nizoka, or with the rights the registry requires in the GitHub organisation of that name (its documentation now asks for an organisation owner). The name shows which GitHub account published the entry; it does not show that the account belongs to the company whose product a server works with.
- Namespace
io.github.Nizoka- Servers with a page
- 2
- Categories
- developer (1), productivity (1)
- Transports
- stdio (local process) (2)
- Package registries
- npm (2)
- Packages declaring environment variables
- 2 of 2
- Websites stated
- github.com (2)
- First published
- 2026-09-07
- Latest update
- 2026-09-24
Source repositories
The 2 repositories these servers state, with how many servers name each, most named first.
| Repository | Servers |
|---|---|
| github.com/Nizoka/pdfnative-mcp | 1 |
| github.com/Nizoka/zipnative-mcp | 1 |
All 2 servers, A to Z
| Server | Runs |
|---|---|
| pdfnative MCP - PDF/A & PDF/X-4 generation, PAdES signing & introspectionPDF MCP: generate PDF/A & PDF/X-4, sign & verify PAdES (LTV), forms, merge, split, encrypt. 28 tools. | Local · stdio |
| zipnative MCP - ZIP creation, inspection, secure extraction & verificationZIP MCP server: create, inspect, verify, extract securely, modify without recompression. 13 tools. | Local · stdio |
Grouped by registry namespace, as the MCP Registry states it. A page here is not an endorsement and nobody pays to be listed: editorial policy · Before you connect a server