Publisher · domain
MCP servers published by dudko.dev
4 servers in the official MCP Registry are published under the namespace dev.dudko/ and have a page in this directory: 2 remote, reached by URL, and 2 run locally from a package. First published 2026-09-25; latest update 2026-09-25.
What this publisher publishes
Names under dev.dudko/ can only be published by someone who has proved control of the domain dudko.dev to the MCP Registry, through a DNS record or a file served over HTTP. The name shows who controls that domain; it does not show that the servers were reviewed.
- Namespace
dev.dudko- Servers with a page
- 4
- Categories
- developer (2), productivity (2)
- Transports
- stdio (local process) (2), Streamable HTTP (2)
- Package registries
- npm (2)
- Remote servers declaring a header
- 0 of 2
- Packages declaring environment variables
- 0 of 2
- Websites stated
- baton.dudko.dev, pdf2md.dudko.dev, tabellum.dudko.dev, vectorize.dudko.dev
- First published
- 2026-09-25
- Latest update
- 2026-09-25
Source repositories
The 4 repositories these servers state, with how many servers name each.
All 4 servers, A to Z
| Server | Runs |
|---|---|
| BatonLocal MCP server for Baton: edit git-native API requests, collections, environments and scripts. | Local · stdio |
| PDF to MarkdownHosted MCP front door to the pdf2md API: checked PDF-to-Markdown requests, short-lived credential. | Remote · HTTP |
| TabellumMCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app. | Local · stdio |
| VectorizeHosted MCP front door to the Vectorize API: raster-to-vector tracing to SVG, PDF, EPS or DXF. | Remote · HTTP |
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