Publisher · GitHub account
MCP servers published by tracegazer
2 servers in the official MCP Registry are published under the namespace io.github.tracegazer/ and have a page in this directory: both run locally from a package. First published 2026-06-09; latest update 2026-06-09.
What this publisher publishes
Names under io.github.tracegazer/ can only be published by someone who signs in to the MCP Registry as the GitHub user tracegazer, or as a member of the GitHub organisation of that name. 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.tracegazer- Servers with a page
- 2
- Categories
- other (2)
- Transports
- stdio (local process) (2)
- Package registries
- OCI image (Docker) (2), PyPI (2)
- Packages declaring environment variables
- 2 of 2
- Websites stated
- github.com (2)
- First published
- 2026-06-09
- Latest update
- 2026-06-09
Source repositories
The 2 repositories these servers state, with how many servers name each.
All 2 servers, A to Z
| Server | Runs |
|---|---|
| Clockify Time TrackingClockify time-tracking MCP: 112 tools across 18 domains, read-only by default with opt-in writes. | Local · stdio |
| InvGate Service DeskInvGate Service Desk MCP: 96 tools/11 domains, 3-tier access (none/support/full), OTel. | 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