noname-mcp-ru
Related Servers
Alternatives to noname-mcp-ru
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to search and retrieve hh.ru vacancies, resumes, employer profiles, salary statistics, ATS/application data, and reference directories across Russia and CIS.55365 npmMIT
- AlicenseAqualityBmaintenanceEnables searching and retrieving job vacancies, resumes, employers, and salary statistics from the hh.ru API (Russia/CIS) via 19 tools, with optional token access for resume search.19140 npm4MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to access and manage HeadHunter job platform data, including vacancies, resumes, negotiations, and employer settings via 167+ tools.165 npm5MIT
- 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.31MIT
- 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
- 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-
TDQS
Scored across 18 tools
Tools are clearly separated into catalog exploration (list_sections, get_section, describe_method, search_methods, map), execution (call/write/delete_method, raw variants, fetch_all), and cabinet management (list/remove/add/set_key/use_cabinet, check_auth). Some naming overlap like get_section vs get_raw could cause confusion, but descriptions disambiguate catalog-based versus raw endpoints.
All tools share the hh_ prefix and use snake_case. Most follow a verb_noun pattern (list_sections, describe_method, add_cabinet), though 'map' and 'fetch_all' deviate slightly. The pattern is predictable and readable overall.
18 tools is on the higher end but appropriate for a comprehensive API wrapper that covers catalog discovery, execution (read/write/delete), raw fallbacks, pagination, and multi-cabinet credential management. The count reflects the API's complexity without being excessive.
The surface covers the full workflow: discover endpoints, execute any verb, handle pagination, manage credentials/cabinets, and check auth. Raw tools provide escape hatches for uncatalogued endpoints. Minor gaps (e.g., no explicit rate-limit handling) are non-critical for typical use.