Trackly CLI
Spec Support Unverified Confidence: Good (0.85)Trackly CLI is an MCP server published by trackly-app; its MCP spec-revision support has not been verified yet. Last verified 2026-08-07.
Does Trackly CLI support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Trackly CLI supports (as of 2026-08-07).
Is Trackly CLI a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Trackly CLI (as of 2026-08-07).
How do I connect to Trackly CLI?
Trackly CLI is available via a hosted remote endpoint at https://mcp.usetrackly.app/api/mcp, the package npm:trackly-cli, the official MCP Registry under io.github.trackly-app/trackly, the source repository at https://github.com/trackly-app/trackly-cli. Authentication: oauth. Transports: streamable-http.
When were Trackly CLI's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
AI job search for Claude, ChatGPT, Cursor. 170K+ jobs, 3,800+ companies. OAuth or stdio.
How widely adopted is Trackly CLI?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.trackly-app/trackly at version 0.13.3 - lists remote endpoint https://mcp.usetrackly.app/api/mcp and repository https://github.com/trackly-app/trackly-cli - accessed
- Endpoint probe of https://mcp.usetrackly.app/api/mcp - authorization required (HTTP 401, Bearer error="invalid_token", error_description="Missing Aut); capability set not observable without credentials - accessed