Publisher portfolio
lazyants
Explore the MCP servers published by lazyants, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 3
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 0
Active servers with a recorded connection probe
- Latest probe connected
- 0
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 3
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
io.github.lazyants/hetzner MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more. | Not measured | Not measured | 4 / 6 | Not checked yet |
io.github.lazyants/lexware MCP server for the Lexware Office API — invoices, contacts, articles, and vouchers. | Not measured | Not measured | 4 / 6 | Not checked yet |
io.github.lazyants/transkribus Transkribus REST and Processing APIs — collections, HTR/OCR; default v1, optional v2 beta. | Not measured | Not measured | 4 / 6 | Not checked yet |
Company & identity
About lazyants
lazyants publishes MCP servers under the io.github.lazyants namespace. This namespace is associated with a GitHub login in the MCP Registry.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.