career_monitor
Related Servers
Alternatives to career_monitor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search job vacancies, manage resumes, and apply to jobs on HeadHunter (hh.ru), Russia's largest job search platform. Includes OAuth 2.0 integration for secure job applications and an automated vacancy hunter agent with intelligent matching.30MIT
- AlicenseAqualityBmaintenanceEnables LLM agents to query and analyze hh.ru job vacancies via full-text and semantic search, with tools for vacancy lookup, skill statistics, market overview, and candidate profile comparison.7MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Desktop or compatible editors to run local, privacy-first job-search workflows including resume generation and STAR polishing, JD matching, GitHub project recommendations, mock interviews, and application tracking. It exposes these capabilities as callable tools through the Model Context Protocol.71MIT
- FlicenseAqualityDmaintenanceEnables to interact with hh.ru (a Russian job platform) through browser automation, allowing users to search for jobs, manage resumes, apply to vacancies with cover letters, and track application statuses via natural language.93-
- AlicenseNot gradedqualityBmaintenanceEnables DeepSeek Harness agents to control a real Jiey Browser instance via MCP, providing tools for web navigation, interaction, and data extraction.166 npm1MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to access and manage HeadHunter job platform data, including vacancies, resumes, negotiations, and employer settings via 167+ tools.165 npm5MIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of ambiguity or overlap between tools. The single 'monitor' tool clearly bundles all control actions, making selection trivial.
With a single tool, there are no naming conventions to compare or contradict. The name 'monitor' is a simple verb that broadly reflects its purpose, though it is somewhat vague, consistency is perfect.
A single tool for a niche monitoring purpose is borderline; it works but feels thin for the variety of actions (start, stop, login, etc.) it claims to handle. The server could benefit from separating concerns into distinct tools, but the count is not extreme.
The tool covers the main lifecycle actions (start, stop, check, login), but lacks configuration options such as customizing the search query or notification filters. It also depends on external setup, leaving gaps that could cause agent failures when specific monitoring needs arise.